0

I'm working on a project, where I cannot disclose the details of the code. So, the application is all written in C and C++. Since, a particular file which wanted to debug has a lot of dependencies and exports, I need to debug the whole project. How do I set breakpoints in the code itself so that the debugging would stop at that particular point? I'm using Ubuntu 14.04 (since the project is compatible with this environment) and gdb debugger.

I've tried using

#include <csignal>

// Generate an interrupt
std::raise(SIGINT);

But I keep getting error

error: ‘raise’ is not a member of ‘std’

Even this also didn't work

#include <signal.h>
raise(SIGINT);

Plus the debugging wont stop at that point, so that I could foresee the function at that point. I only want to debug it from console, rather using any IDE.

Since the programfile I want to debug has lot many header files which it imports, I'm unable to make a executable to use gdb. So, while make clean build of my MakeFile I want to debug the particular program file at a particular function. So, for that I want to add breakpoints in the program. I cannot use any GUI for debugging since I should not use.

Lundin
  • 195,001
  • 40
  • 254
  • 396
Jackelyn
  • 21
  • 2
  • Your Ubuntu 14 is *really old* and you should upgrade it (current Ubuntu is [18.04](https://www.ubuntu.com/download/desktop) in october 2018) – Basile Starynkevitch Oct 17 '18 at 05:13
  • @BasileStarynkevitch Ikr – Jackelyn Oct 17 '18 at 05:13
  • Please [edit](https://stackoverflow.com/posts/52847568/edit) your question to **add several paragraphs of motivation and context**. Why do you need to add breakpoints inside your C code? Why cannot you run `gdb` non-interactively, with some script (perhaps from your `Makefile`?)? Without these explanations, your question is unclear. – Basile Starynkevitch Oct 17 '18 at 05:58
  • 1
    You set the breakpoints in your debugger, not in the source code. – Jesper Juhl Oct 17 '18 at 06:02
  • 1
    Your question is very unclear and shows a lot of confusion. Build your program on the command line. Show the compilation commands and some [MCVE] in your question – Basile Starynkevitch Oct 17 '18 at 08:28
  • It seems that you are very unfamiliar with best (or even current) practices in C and/or C++. I strongly recommend studying the source code of some small free software applications (perhaps similar to yours) for Linux. You'll find many of them e.g. on [github](http://github.com/) – Basile Starynkevitch Oct 17 '18 at 13:45

3 Answers3

1

Have you tried to use GDB Commands?
b lineno - set a break point at line 'lineno' b srcfile:lineno - set a break point in source file 'srcfile' at line 'lineno'

Andersen
  • 93
  • 10
0

Read more about debugging with gdb. Be sure to compile all your code with DWARF debug information (so use g++ -Wall -Wextra -g to compile it with GCC).

GDB is extensible and you can define your own gdb commands at startup in your init file, probably .gdbinit and put some initial commands there.

BTW, on Linux, debugging (so the gdb debugger) is using ptrace(2) facilities. And you can use gdb non-interactively on the command line, using scripts.

How do I set breakpoints in the code itself

I don't recommend adding specific C code for breakpoints. So don't do that in your C code. But see also this.

Perhaps you want some backtrace library, like Ian Taylor's libbacktrace ?

I cannot use any GUI for debugging

You don't need to. You'll use gdb on the command line. With an appropriate gdb script, you can even use it non-interactively (e.g. in a Makefile)

I only want to debug it from console, rather using any IDE.

Please realize that IDEs are only glorified source code editors capable of running other external tools (including the GCC compiler and the gdb debugger). You certainly don't need -on Linux- any IDE to run a compiler or a debugger (but IDEs could be convenient, but not necessary, for that), because you can (and should) run your compiler, your debugger, your build automation tool, on the command line.

Since the program file I want to debug has lot many header files which it imports, I'm unable to make a executable

You should fix that first. You need to make an executable. BTW, there is no "import" involved at run time, since header files are relevant only at compile time. Read more about the cpp preprocessor. You probably should invoke GCC (e.g. the g++ compiler, since you have C++ code) with appropriate preprocessor options (sometimes, tools like pkg-config are useful for that). You probably should use some build automation tool such as GNU make (with your Makefile; see this for inspiration) or ninja. You could add ad hoc gdb commands to your build procedure (e.g. with some additional and specific rules and/or recipes in your Makefile).

Basile Starynkevitch
  • 223,805
  • 18
  • 296
  • 547
  • it is more while building the project itself the program gets debugged, so I wanted to put the breakpoint in the program. – Jackelyn Oct 17 '18 at 05:43
  • Wrong approach. Your building procedure should run `gdb` with an appropriate script. Don't try to add breakpoints programmatically in C. BTW, you might explain why you want to debug your program at build time (it is an usual requirement) – Basile Starynkevitch Oct 17 '18 at 05:50
  • I have a programfile which is a part of the project, which inturn has many headerfiles to import. So individually I could not make a exe file to use gdb. – Jackelyn Oct 17 '18 at 05:52
  • If you don't have an executable, you cannot run a debugger. So you need to improve your build procedures to use executables (even "temporary" ones) – Basile Starynkevitch Oct 17 '18 at 05:54
0

First, make sure you have compiled with -g. There are other gdb specific flags in gcc. You could add them in too.

Try using ddd, the graphical version of gdb. Great tool if you don't know the gdb command line. Just open up the relevant source file, select the line then click on breakpoint on the toolbar. It will tell you on the console section, what command was actually executed (good way to learn). There is a floating button list with run, next etc. for stepping through your code.

ddd will work on most of the gcc toolchain.

EDIT: Say your code is made up of 2 files main.cpp and child.cpp. main.cpp contains main(). The executable is called a.out.

To start

ddd a.out &

It will open in main.cpp. To put a breakpoint in child.cpp, click on File/Open Source... and select child.cpp. Then scroll to where you want a breakpoint. Put your cursor on the line, then click on break in the toolbar.

To run, either type run in the gdb window below or click on Run in the floating button dialog.

cup
  • 7,589
  • 4
  • 19
  • 42