Debugger didn't retrieve the source code from debuging info

[DigitalBox98]

In some situations, the Debugger is not able to retrieve the source code of the program.

In the example attached, putting the break point in the About dialog part is not attaching it in the source code. The breakpoint is working however the source code is not more displayed after that.

Attached example : SimpleOpenGLCube : working example (Debugger is able to work with the source code) SimpleApp : example where Debugger is not able to retrieve the source code once the main is runned

[DigitalBox98]

Initial run working OK (source displayed)

[DigitalBox98]

Putting breaking in the AboutDialog is not attached to the source code for an unknown reason

[DigitalBox98]

Once the breakpoint is reached, no source code is diplayed

[DigitalBox98]

The application source code is no more found by the Debugger

[DigitalBox98]

SimpleApp source code to reproduce the issue

[DigitalBox98]

Example where Debugger is working without any issue

[DigitalBox98]

I'm closing this ticket as it's more relative to the build phase : if directory is not referenced in the debug infos, we can manually indicates to Debugger where to look for?.

[nephele]

I'm confused, the issue is still present, no?

[anevilyak]

From the description it's a bit unclear what the problem is ; the problem with source file location is it depends a lot on exactly what the compiler embeds in the DIE ; in some cases I've seen gcc only embed a relative path e.g. src/abc/def/file.cpp or sometimes even with ... In cases such as this the debugger has no way of knowing what the base path for locating those is supposed to be, so it has to rely on the working directory the binary is run from to try to find them. If the problem is that it's displaying disassembly and giving you the option to locate the source file, that sounds like working as designed, because that's the most it can do given the info it has, but if it's either displaying nothing at all, or disassembly with no option to help it find the file, then that's an issue. Clarification needed.

[waddlesplash]

Somehow GDB manages to figure this out much more of the time than Debugger is, so clearly there's some way to make it work.

Automatic finding of source code basically never works for me in Debugger at present. A lot of the time it actually displays the absolute path the compiler was run from (e.g. "/boot/home/Desktop/haiku/generated/") combined with the source filename (e.g. "File.cpp") without the intermediate path (e.g. "../src/kits/storage"). That sounds to me like some DWARF information is being ignored or misused.

[anevilyak]

What DWARF version? I definitely had this working fine for DWARF 4.

[waddlesplash]

Whatever the default is with our GCC 13. I think we tried to set DWARF 4 but may get DWARF 5 for certain things.

[DigitalBox98]

I need to double check again this specific case when I have access to the machine where Haiku is installed.

SimpleApp.zip should contain all the details to reproduce the issue : execute "compile" script and then launch Debugger ./MyApp to check if it's possible to access the source code when debugging (like breakpoint in the About part)

[DigitalBox98]

I confirm there's an issue with the SimpleApp.zip

To reproduce it's quite simple :

1. Compile the program by launching the script :

./compile

2. File is having debug info :

file ./App

3. Launch Debugger on it :

Debugger ./App

4. First issue : the main() from App.cpp is not displayed in the Debugger, instead the source code WindowApp.cpp is displayed (this cpp file has nothing to do with the main())
5. Second issue : click on "Run" then "Debug" button, the message "Source file unavailable" is displayed and it's impossible to attach the corresponding source file in the Debugger (I've tried to click on the "Source file unavailable" line in order to change it...)

Let me know if you need more details.

[pulkomandy]

What DWARF version? I definitely had this working fine for DWARF 4.

In case that matters, there were changes in Haiku build system some time ago. Before these changes, the compiler was passed absolute paths to sourcefiles, and these paths ended up directly in the debug info. Now, we pass relative paths on the command line, and these get in the debug info instead.

Was Debugger also tested with this use of the compiler?

[anevilyak]

It was, that's what webkit did back when I fixed a bunch of issues to get that working.