Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Cc: Doug Evans <dje@google.com>
Subject: Advice on fixing gdb/12528
Date: Fri, 11 Mar 2011 17:09:00 -0000	[thread overview]
Message-ID: <AANLkTim5vFBo4=mP7-83dqKbmuMAP3ThS6ZW_VN3rjg4@mail.gmail.com> (raw)

Greetings,

Doug and myself just independently hit
http://sourceware.org/bugzilla/show_bug.cgi?id=12528 (and 12568).

I would like advice on fixing it.

I know that in general GDB can not ignore code at location 0,
but it appears inevitable that it must do so on platforms where
- it is known that no code can execute there, and
- linker relocates debug info to address 0 to indicate that
  the corresponding code has been discarded.

So would something like:

 case DW_LNE_set_address:
   address = read_address (abfd, line_ptr, cu, &bytes_read);
   if (!target->to_valid_code_address (address)) {
      // this debug line info corresponds to function that has
      // been GCd by the linker.  Skip to end_sequence.
   }

in dwarf_decode_lines() ?

Thanks,
-- 
Paul Pluzhnikov


             reply	other threads:[~2011-03-11 16:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 17:09 Paul Pluzhnikov [this message]
2011-03-11 18:27 ` Tom Tromey
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='AANLkTim5vFBo4=mP7-83dqKbmuMAP3ThS6ZW_VN3rjg4@mail.gmail.com' \
    --to=ppluzhnikov@google.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /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