http://bugs.winehq.org/show_bug.cgi?id=18628
Sylvain Pasche sylvain.pasche@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #7 from Sylvain Pasche sylvain.pasche@gmail.com 2009-05-31 08:46:39 --- Yes, that's now fixed, thanks.
That's not totally related, but I'm getting lots of fixme messages when the symbols are read:
fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported form for const value one (a) fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported form for const value two (a) fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported form for const value erx (a) [...] fixme:dbghelp_dwarf:compute_location Unhandled attr op: e0 fixme:dbghelp_dwarf:compute_location Unhandled attr op: e0 fixme:dbghelp_dwarf:compute_location Unhandled attr op: e0 [...]
Should I file a new bug for this?
The "Unsupported form for const" message is a DW_FORM_block1 attribute that falls through the switch in dwarf2_parse_variable.
The "Unhandled attr op" message is about a GNU extension (DW_OP_GNU_push_tls_address opcode). Maybe this one should just be ignored (or better, ignore all the extensions if that's possible).