Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] minimal symbols on mips-irix and overlapping CUs...
Date: Sat, 22 Nov 2003 18:54:00 -0000	[thread overview]
Message-ID: <3FBFB0C7.4050409@gnu.org> (raw)
In-Reply-To: <20031118012558.GD8608@gnat.com>

> But Joel's case did have debugging information, I think - so just the
>> minsyms are missing?
> 
> 
> Yes, that's right. And one interesting thing I did find: "nm" on
> mips-irix dumps the symbol from the symbol table AND the dwarf-2
> info...

What about the ".pdr" section?

I get the feeling that core GDB has another really useful table just 
beyond its fingertips - the unwind table - and that can be used to find 
things like map from a pc to the function start/end/name/...:

- PPC64 has a traceback table just past the end of the function and that 
can provide a pointer (tb_offset) back to the function's start

- For ia64, it must have similar (for that binary search to work)

- For MIPS there's this PDR section and it appears to have the function 
start as well.

Andrew



  reply	other threads:[~2003-11-22 18:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 22:39 Joel Brobecker
2003-11-17 23:35 ` Daniel Jacobowitz
2003-11-18  0:25   ` Andrew Cagney
2003-11-18  0:28     ` Daniel Jacobowitz
2003-11-18  1:25       ` Joel Brobecker
2003-11-22 18:54         ` Andrew Cagney [this message]
2003-11-23  1:14           ` Daniel Jacobowitz
2003-11-23  4:04             ` Joel Brobecker
2003-11-18  1:24   ` Joel Brobecker
2003-11-18  1:33     ` Daniel Jacobowitz
2003-11-23 20:00 David Anderson

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=3FBFB0C7.4050409@gnu.org \
    --to=cagney@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.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