First: are you compiling *all* modules with -gc rather than -g?
Ah ok, somehow I was mislead into thinking that the gdb patches allow you to use -g.
It works now though line numbers are more messed up than I'm used to from cv2pdb + VS. There I only have the usual problems with mixins but here it even jumps around senselessly if I just do a step over.
Don't know if this has to do with -gc or Descent.
To do that, I recommend you unleash DustMite on your source: https://github.com/CyberShadow/DustMite. You'll need a script that can test for the bug too, you can pass a command file to gdb and grep for the relevant failure, alternatively if you can get the failure when using dwarfdump/objdump that may be easier.
Yeah need to test that tool soon.
