I'm about to overhaul dmd's DWARF information and will try to fix the outstanding issues. It seems (subjective) that the current state is worse than a year ago.
So in any case we'll need a test suite to avoid regressions.
In the best case we find/write a tool that verifies correct debug information.
Otherwise we could try to automate gdb sessions but this is probably a very slow test.
Comment #1 by code — 2013-11-30T13:29:33Z
A simple solution would be to process the output of readelf or dwarfdump.
Comment #2 by andrei — 2014-01-10T17:32:11Z
$50 bounty placed
Comment #3 by ibuclaw — 2014-02-14T02:41:31Z
Martin, wouldn't that be very DMD-specific?
Only ask because currently I'm in the process of writing a lot of tests for the GDB testsuite to ensure that GDB behaves correctly for both gdb sessions and evaluating expressions sent to GDB.
Comment #4 by code — 2014-02-14T03:03:12Z
Yeah, that could easily turn into somethin DMD specific.