User forums > Help

[FIXED] Debugger issue [update of gdb needed]

<< < (4/4)

thierryv:

--- Quote from: BlueHazzard on August 31, 2022, 06:06:30 pm ---From your last log

--- Quote ---[debug][Thread 4760.0x2dbc exited with code 0]
[debug][Inferior 1 (process 4760) exited normally]
--- End quote ---
This indicates that your program exits before it reaches the breakpint...
Try to add the breakpoint at the first line in the main function and then single step trough (not by using the red arrow, but the single step button)

--- End quote ---

ok, when i do as you describe it works !
not very practical, but functional in any case! ! YEAH
Thanks, I was getting desperate.

BlueHazzard:
Of cours you can do bisectional search with break points to find the point where your application exits.
Also make sure you have deactivated all code optimization so not that you put a break point in a line that gets optimized away from the compiler and debugger can not break on it

AndrewCot:
GDB 8.1 has issues like the one reported. As such please update to a later version (at least use V9 or preferably 11 or 12). The latest GDB is V12.1, but not all compiler toolchains have this version yet.

If you cannot get a later version for the compiler toolchain you are using then try the latest from the following github repo:

* https://github.com/ssbssa/gdb/releases

thierryv:

--- Quote from: AndrewCot on August 31, 2022, 11:56:51 pm ---GDB 8.1 has issues like the one reported. As such please update to a later version (at least use V9 or preferably 11 or 12). The latest GDB is V12.1, but not all compiler toolchains have this version yet.

If you cannot get a later version for the compiler toolchain you are using then try the latest from the following github repo:

* https://github.com/ssbssa/gdb/releases

--- End quote ---

--- Quote from: BlueHazzard on August 31, 2022, 09:24:16 pm ---Of cours you can do bisectional search with break points to find the point where your application exits.
Also make sure you have deactivated all code optimization so not that you put a break point in a line that gets optimized away from the compiler and debugger can not break on it

--- End quote ---

I will try does two advices, thanks for your time and feedback ! 

thierryv:

--- Quote from: AndrewCot on August 31, 2022, 11:56:51 pm ---GDB 8.1 has issues like the one reported. As such please update to a later version (at least use V9 or preferably 11 or 12). The latest GDB is V12.1, but not all compiler toolchains have this version yet.

If you cannot get a later version for the compiler toolchain you are using then try the latest from the following github repo:

* https://github.com/ssbssa/gdb/releases
--- End quote ---

Moreover, it would seem that with the recommended update of gdb, it works (for the moment), thanks again for everything.

Navigation

[0] Message Index

[*] Previous page