(Another) breakpoint not getting hit, presumably because it's in a generated source file?

[conversy]

Hi,

I set up a breakpoint in the source code of a generated source file (generated from another source). The generated source code is in a build/ directory.

When I launch the debugger, the entry in the BREAKPOINTSsection of VSCode is grayed out, with a tooltip saying "Resolved location: 0".

I had a look at the wiki's troubleshootings topic on that matter, tried everything, to no avail.

I actually could make the function breakpoint (with main, as it belongs to the faulty generated source file) or stopOnEntry work, even if it does not display the source code (only the disassembled code), and used breakpoint list --verbose to see which file the function belongs to, e.g.

with function breakpoint main:

Console is in 'commands' mode, prefix expressions with '?'.
Launching: /Users/conversy/recherche/istar/code/djnn/smala/build/cookbook/gui/direct_manipulation/simplest/simplest_app
Launched process 27084
breakpoint list --verbose
Current breakpoints:
1: file = '/Users/conversy/recherche/istar/code/djnn/smala/build/cookbook/gui/direct_manipulation/simplest/simplest.cpp', line = 51, exact_match = 0


2: name = 'main'

    2.1: 
      module = /Users/conversy/recherche/istar/code/djnn/smala/build/cookbook/gui/direct_manipulation/simplest/simplest_app
      compile unit = simplest.cpp
      function = main
      location = /Users/conversy/recherche/istar/code/djnn/smala/cookbook/gui/direct_manipulation/simplest/simplest.cpp:25:2
      address = 0x0000000100003554
      resolved = true
      hardware = false
      hit count = 1   

with stopOnEntry:

Launching: /Users/conversy/recherche/istar/code/djnn/smala/build/cookbook/gui/direct_manipulation/simplest/simplest_app
Launched process 26467
Stop reason: signal SIGSTOP
breakpoint list --verbose
Current breakpoints:
1: file = '/Users/conversy/recherche/istar/code/djnn/smala/build/cookbook/gui/direct_manipulation/simplest/simplest.cpp', line = 51, exact_match = 0

But at this point I do not know what to do.

The thing is, I could make some similar setup work in another project, but I cannot figure out the difference.

OS: MacOS 12.4
VSCode version: 1.71.0 (Universal)Commit: 784b0177c56c607789f9638da7b6bf3230d47a8c
CodeLLDB version: v0.2.3
Compiler: clang Apple clang version 13.1.6 (clang-1316.0.21.2.5) arm64-apple-darwin21.5.0
Debuggee: lldb-1316.0.9.46

[vadimcn]

Did you set up source mapping? You can use show_debug_info simplest_app --verbose command to display what paths got encoded in the debug info.

[conversy]

Yes, I did try to setup source mapping, and sometimes the breakpoint is hit, but the source is not displayed, I only get assembly.

show_debug_info simplest_app --verbose leads to this:

show_debug_info simplest_app --verbose
Module /Users/conversy/recherche/istar/code/djnn/smala/build/cookbook/gui/direct_manipulation/simplest/simplest_app : 1 compile units with debug info
    /Users/conversy/recherche/istar/code/djnn/smala/build/cookbook/gui/direct_manipulation/simplest/simplest.cpp

Namespace(verbose=True, mod_name='simplest_app')

well, does it mean there is no debug info in the binary?

[vadimcn]

Does the source file exist at that path? Can you do cat /Users/conversy/recherche/istar/code/djnn/smala/build/cookbook/gui/direct_manipulation/simplest/simplest.cpp?

[conversy]

yes it does, cat works, but as I said, simplest.cpp is generated, so it may disappear after a make clean, or because it is considered intermediate by make.
However in another similar project, I have no problem setting a breakpoint in a similarly generated file, so it's very strange...
There is something odd that I might be missing, but I cannot find out what.

[vadimcn]

Sorry, I don't know what's going on... Try poking around, keeping in mind that in order for breakpoint setting to succeed, the path must match the one stored in the debug info exactly (after being transformed via the source map).