From: Tom Tromey <tromey@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>, Doug Evans <dje@google.com>
Subject: Re: Advice on fixing gdb/12528
Date: Fri, 11 Mar 2011 18:27:00 -0000 [thread overview]
Message-ID: <m3wrk560mf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTim5vFBo4=mP7-83dqKbmuMAP3ThS6ZW_VN3rjg4@mail.gmail.com> (Paul Pluzhnikov's message of "Fri, 11 Mar 2011 08:05:29 -0800")
>>>>> "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
next prev parent reply other threads:[~2011-03-11 17:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 17:09 Paul Pluzhnikov
2011-03-11 18:27 ` Tom Tromey [this message]
2011-03-14 21:16 ` [patch] " Paul Pluzhnikov
2011-03-15 3:16 ` Jan Kratochvil
2011-03-15 5:26 ` Paul Pluzhnikov
2011-03-15 15:35 ` Tom Tromey
2011-03-15 15:45 ` Jan Kratochvil
2011-03-15 16:00 ` Paul Pluzhnikov
2011-03-15 18:50 ` Jan Kratochvil
2011-03-15 19:12 ` Paul Pluzhnikov
2011-03-15 19:18 ` Jan Kratochvil
2011-03-15 19:41 ` Paul Pluzhnikov
2011-03-15 23:26 ` Jan Kratochvil
2011-03-16 0:13 ` Paul Pluzhnikov
2011-03-16 8:20 ` Jan Kratochvil
2011-03-16 17:43 ` Paul Pluzhnikov
2011-03-16 17:52 ` Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wrk560mf.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox