Default Debugger issue?

Software Native
21

I’ve cheked today with the official Haiku apps sources, and the issue is the same : from what I can see, the debug files are not well handled.

Below is the use case :
clock application

Activate debugging for apps : build/jam/UserBuildConfig

# Enable debugging for directory src/system/boot/loader recursively.
SetConfigVar DEBUG : HAIKU_TOP src apps : 1 : global ;

Then compile :
jam -q Clock

Then launch debugger from the “generated.x86_64” dir :
Debugger objects/haiku/x86_64/debug_1/apps/clock/Clock

2024-11-14_21-59
2024-11-14_21-591234×650 73.9 KB

No source code is visible.

Versus GDB :

2024-11-14_22-00
2024-11-14_22-00880×694 92.5 KB

So I’m really wondering in which use cases today Debugger is working fine.
So far I’ve got only 1 application recognized by Debugger : a one 1 file application (simple OpenGL app)

Anybody has some success on this ?

I’m currently working on a article on how to generate debug infos for haiku official apps and the way to debug them.
EDIT : I will advice both Debugger and GDB

1 Like
22

Again, for specific issues please open tickets.
Dwarf5 is implementef iirc, so a lack of implementation is not the problem. Potentially problems with it still exist (but then you can tell gcc to use a previous dwarf format too.)

https://cgit.haiku-os.org/haiku/log/src/kits/debugger

Have you actually tried the “Click to locate source file” option?

Presumeably gdb in qt creator, in the context of a project, has to know where the source file is… But i don’t see how you expect Debugger to figure this out without info

1 Like
23

What do you mean by “Click to locate source file” option.

Maybe I don’t know this feature, but I can’t see this in Debugger.

24

Ok I find something : if I put the source files in the directory “generated.x86_64” ii’s working fine !

So maybe it’s something relative to how Debugger is determining the sources directory to look for, or another option is that during the build the directory indicated is not accurate ? (I don’t know if debug info are putting directory location for files)

1 Like
25

Notice that line of text below the “Run” / “Step over” / “Step into” / “Step out” buttons on your screenshot of Debugger debugging Clock.

1 Like
26

From your screenshot

2024-11-14_21-59 2
2024-11-14_21-59 21234×650 103 KB

1 Like
27

Ok got it thanks ! So I confirm it’s working fine now.

The “issue” seems to be relative to the build :
“jam -q Clock” is considering the sources files are in “generated.x86_64” instead of “src/apps/clock” hence the confusion + I didn’t see that nice feature to select the sources path.

1 Like
28

Perhaps this can be made a bit more prominent, to indicate this is an actionable item and not an informative text string

2 Likes
29

A thing to note here, when apps crash the “generate report” option is quite helpfull for debugging the OS, it gives a text readable backtrace etc for upload, compared to a core dumb the debug symbols are only needed on the generting system, not for the insoecting person (and the report is readable online directly)

30

Ok thanks for this information, I will report this “generate report” feature

EDIT : I’ve updated the ticket on this issue (#19243 (Debugger didn't retrieve the source code from debuging info) – Haiku) , because there’s a strange behavior in the Debugger which is not able to identify the source file linked to the main() of my SimpleApp.zip application

So in some situations there’s no issue, but there are still cases to investigate.

31

I have experienced similar issues. Somehow I got it working once, but not anymore.
I’m on latest nightly as of today and use Genio.
Debugger cannot find the source, and I cannot find the select button (see screenshot).
GDB works fine and sees the source, but is a PITA to use.

debugger-no-src
debugger-no-src1672×1080 171 KB

senity-debug-gdb
senity-debug-gdb1185×699 76.5 KB

Also tried a manual make (as opposed to Genio build) with explicit DEBUG setting in Makefile:


#   Specify all the preprocessor symbols to be defined. The symbols will not
#       have their values set automatically; you must supply the value (if any) to
#       use. For example, setting DEFINES to "DEBUG=1" will cause the compiler
#       option "-DDEBUG=1" to be used. Setting DEFINES to "DEBUG" would pass
#       "-DDEBUG" on the compiler's command line.
DEFINES = DEBUG=1

#       With image symbols, stack crawls in the debugger are meaningful.
#       If set to "TRUE", symbols will be created.
SYMBOLS := TRUE

#       Includes debug information, which allows the binary to be debugged easily.
#       If set to "TRUE", debug info will be created.
DEBUGGER := TRUE