search for: dwarf2read

...bug_frame, past simple parsing? Anything else requires real evaluation. I ask because I wrote a DWARF reader that google uses internally, and then was open sourced and contributed to google breakpad. (see http://code.google.com/p/google-breakpad/source/browse/trunk/src/common/dwarf/, in particular dwarf2reader.cc). > 2. Relying of assembly directive emissions (i.e. .cfi_*), which is > cumbersome and misses a lot of things like actual DWARF encoding. Err, .cfi_ and used because the encoding is tricky to get right, and assemblers are better at optimizing it. However, i'll point out that break...

...le-darwin (symbol_file_add_name_with_addrs_or_offsets+0x7a) [0x563c9] >> [ 11 ] /usr/libexec/gdb/gdb-i386-apple-darwin (symbol_file_add_main_1+0xf2) [0x56e36] >> [ 12 ] /usr/libexec/gdb/gdb-i386-apple-darwin (catch_command_errors+0x4d) [0x7ac88] >> /SourceCache/gdb/gdb-966/src/gdb/dwarf2read.c:7593: internal-error: could not find partial DIE in cache >> >> A problem internal to GDB has been detected, >> further debugging may prove unreliable. >> Quit this debugging session? (y or n) >> >> Now, all of this was working earlier, and I don't know...

...darwin > (symbol_file_add_name_with_addrs_or_offsets+0x7a) [0x563c9] > [ 11 ] /usr/libexec/gdb/gdb-i386-apple-darwin (symbol_file_add_main_1+0xf2) > [0x56e36] > [ 12 ] /usr/libexec/gdb/gdb-i386-apple-darwin (catch_command_errors+0x4d) > [0x7ac88] > /SourceCache/gdb/gdb-966/src/gdb/dwarf2read.c:7593: internal-error: could > not find partial DIE in cache > > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Quit this debugging session? (y or n) > > > Now, all of this was working earlier, and I don't know whether it was &g...

...sr/libexec/gdb/gdb-i386-apple-darwin (symbol_file_add_name_with_addrs_or_offsets+0x7a) [0x563c9] [ 11 ] /usr/libexec/gdb/gdb-i386-apple-darwin (symbol_file_add_main_1+0xf2) [0x56e36] [ 12 ] /usr/libexec/gdb/gdb-i386-apple-darwin (catch_command_errors+0x4d) [0x7ac88] /SourceCache/gdb/gdb-966/src/gdb/dwarf2read.c:7593: internal-error: could not find partial DIE in cache A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) Now, all of this was working earlier, and I don't know whether it was something I did or a change in LLVM, bu...

...gdb-i386-apple-darwin (symbol_file_add_name_with_addrs_or_offsets+0x7a) [0x563c9] > [ 11 ] /usr/libexec/gdb/gdb-i386-apple-darwin (symbol_file_add_main_1+0xf2) [0x56e36] > [ 12 ] /usr/libexec/gdb/gdb-i386-apple-darwin (catch_command_errors+0x4d) [0x7ac88] > /SourceCache/gdb/gdb-966/src/gdb/dwarf2read.c:7593: internal-error: could not find partial DIE in cache > > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Quit this debugging session? (y or n) > > Now, all of this was working earlier, and I don't know whether it was something...

...#39;t support debug_frame, as one relevant example. > I ask because I wrote a DWARF reader that google uses internally, and > then was open sourced and contributed to google breakpad. > (see http://code.google.com/p/google-breakpad/source/browse/trunk/src/common/dwarf/, > in particular dwarf2reader.cc). > >> 2. Relying of assembly directive emissions (i.e. .cfi_*), which is >> cumbersome and misses a lot of things like actual DWARF encoding. > > Err, .cfi_ and used because the encoding is tricky to get right, and > assemblers are better at optimizing it. > However...

...darwin > (symbol_file_add_name_with_addrs_or_offsets+0x7a) [0x563c9] > [ 11 ] /usr/libexec/gdb/gdb-i386-apple-darwin (symbol_file_add_main_1+0xf2) > [0x56e36] > [ 12 ] /usr/libexec/gdb/gdb-i386-apple-darwin (catch_command_errors+0x4d) > [0x7ac88] > /SourceCache/gdb/gdb-966/src/gdb/dwarf2read.c:7593: internal-error: could > not find partial DIE in cache > > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Quit this debugging session? (y or n) > > > Now, all of this was working earlier, and I don't know whether it was &g...

...file_add_name_with_addrs_or_offsets+0x7a) [0x563c9] >> [ 11 ] /usr/libexec/gdb/gdb-i386-apple-darwin >> (symbol_file_add_main_1+0xf2) [0x56e36] >> [ 12 ] /usr/libexec/gdb/gdb-i386-apple-darwin (catch_command_errors+0x4d) >> [0x7ac88] >> /SourceCache/gdb/gdb-966/src/gdb/dwarf2read.c:7593: internal-error: could >> not find partial DIE in cache >> >> A problem internal to GDB has been detected, >> further debugging may prove unreliable. >> Quit this debugging session? (y or n) >> >> >> Now, all of this was working earlier, and I...

Hi All, While working on some recent patches for x32 support, I ran into an unpleasant limitation the LLVM eco-system has with testing DWARF emission. We currently have several approaches, neither of which is great: 1. llvm-dwarfdump: the best approach when it works. But unfortunately lib/DebugInfo supports only a (small) subset of DWARF. Tricky sections like debug_frame aren't supported. 2.

...file_add_name_with_addrs_or_offsets+0x7a) [0x563c9] >> [ 11 ] /usr/libexec/gdb/gdb-i386-apple-darwin >> (symbol_file_add_main_1+0xf2) [0x56e36] >> [ 12 ] /usr/libexec/gdb/gdb-i386-apple-darwin (catch_command_errors+0x4d) >> [0x7ac88] >> /SourceCache/gdb/gdb-966/src/gdb/dwarf2read.c:7593: internal-error: could >> not find partial DIE in cache >> >> A problem internal to GDB has been detected, >> further debugging may prove unreliable. >> Quit this debugging session? (y or n) >> >> >> Now, all of this was working earlier, and I...