------- Comment #28 from developer at sandoe-acoustics dot co dot uk
2009-09-21 16:46 -------
(In reply to comment #27)
> I believe I've caught all DW_OP_{implicit,stack}_value uses in dwarf2out.c, so
> likely -gstrict-dwarf wasn't used when compiling something that has been
> linked
> into those libraries.
(two bootstraps later...)
I jammed an Init(1) into the flag line and the four fail cases still appear.
With current trunk - and dwarf2out.c from 151814 there are no fails.
> No idea if Mach-O has any tools similar to readelf that would allow you to
> dump
> the debug info of object files, if not, you'll need to check for it at the
I'll have to see what dwarfdump can do (one might expect it to fail in the same
way as dsymtuil)
- but first we need a reliable simple failing case.
> assembler level (-save-temps plus -dA).
downloaded the dwarf2 and dwarf3 specs...
ah well, there's always hexdump ;-)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41405
