This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Advice on fixing gdb/12528
- From: Tom Tromey <tromey at redhat dot com>
- To: Paul Pluzhnikov <ppluzhnikov at google dot com>
- Cc: gdb-patches ml <gdb-patches at sourceware dot org>, Doug Evans <dje at google dot com>
- Date: Fri, 11 Mar 2011 10:14:00 -0700
- Subject: Re: Advice on fixing gdb/12528
- References: <AANLkTim5vFBo4=mP7-83dqKbmuMAP3ThS6ZW_VN3rjg4@mail.gmail.com>
>>>>> "Paul" == Paul Pluzhnikov <ppluzhnikov@google.com> writes:
Paul> I know that in general GDB can not ignore code at location 0,
Paul> but it appears inevitable that it must do so on platforms where
Paul> - it is known that no code can execute there, and
Paul> - linker relocates debug info to address 0 to indicate that
Paul> the corresponding code has been discarded.
Paul> So would something like:
Paul> case DW_LNE_set_address:
Paul> address = read_address (abfd, line_ptr, cu, &bytes_read);
Paul> if (!target->to_valid_code_address (address)) {
Paul> // this debug line info corresponds to function that has
Paul> // been GCd by the linker. Skip to end_sequence.
Paul> }
Paul> in dwarf_decode_lines() ?
Can you check the has_section_at_zero flag on dwarf2_per_objfile?
Tom