http://d.puremagic.com/issues/show_bug.cgi?id=3207
--- Comment #5 from Leandro Lucarella <llu...@gmail.com> 2009-08-07 20:53:52 PDT --- Created an attachment (id=436) --> (http://d.puremagic.com/issues/attachment.cgi?id=436) LDC debug output (In reply to comment #4) Jason House wrote (Thu, 06 Aug 2009 07:55:55 -0400): No luck with gdb. Here's something interesting though: $ dmd2/linux/bin/dmd -g main.d -ofmain $ objdump -g main > info.dmd objdump: Warning: .debug_info offset of 0x12c in .debug_pubnames section does not point to a CU header. $ ldc-0.9.1-x86_32/bin/ldc -g main.d $ objdump -g main > info.ldc objdump: Warning: Bogus end-of-siblings marker detected at offset 226 in .debug_info section objdump: Warning: Bogus end-of-siblings marker detected at offset 227 in .debug_info section objdump: Warning: Bogus end-of-siblings marker detected at offset 228 in .debug_info section objdump: Warning: Further warnings about bogus end-of-sibling markers suppressed When comparing the output, I do see that ldc outputs dw_at_subprogram when dmd outputs dw_at_module. I think it's safe to ignore that ldc outputs _D4main16__moduleinfoCtorZ and dmd does not. I see this in the ldc output but not dmd: DW_AT_MIPS_linkage_name DW_FORM_string DW_AT_decl_file DW_FORM_data1 DW_AT_decl_line DW_FORM_data1 DW_AT_low_pc DW_FORM_addr DW_AT_high_pc DW_FORM_addr DW_AT_frame_base DW_FORM_block1 I also see DW_AT_decl_line DW_FORM_data1 (in ldc) DW_AT_decl_line DW_FORM_data2 (in dmd) There's a few other differences, but I nievely thing they're either trivial or related to the above. LDC outputs a few "identical" tags in a slightly different order. I can provide details on that if it'd help. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
