Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Anderson <davea@quasar.engr.sgi.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC] minimal symbols on mips-irix and overlapping CUs...
Date: Sun, 23 Nov 2003 20:00:00 -0000	[thread overview]
Message-ID: <200311231959.hANJxOQs1070080@quasar.engr.sgi.com> (raw)


Joel writes:
|> > - For MIPS there's this PDR section and it appears to have the function 
|> > start as well.
|> 
|> I don't believe that the IRIX tools generate .pdr.  I might be mistaken
|> about that, though.
|
|I confirm. I checked in a few executables, and couldn't find any section
|named .pdr.


Quite right. In IRIX pdr is an area in the o32 mdebug
(third-eye) debug information, not an elf section.

What 'PDR section' above might have referred to:
The Elf section. 
		.rtproc 
is generated in o32 ELF to handle run-time stack walkback, as
in C++ or Ada exceptions.  In header files the struct is RPDR
defined in IRIX '/usr/include/sym.h'.
A run-time pdr, slightly different from an mdebug pdr.  
It is accessed like a variable via the data items
_procedure_table, and _procedure_table_size not thru section
headers (as a runtime feature) (_procedure_table,
procedure_table_size are per shared-library/executable, not
global). The data did not exist unless you asked for it, as in
CC -32 -exceptions, for example.

For o32 we also have (but I am having trouble remembering)
  in /usr/include/sys/elf.h
  #define MIPS_PDR_EXCEPTION     ".MIPS.pdr_exception"
which I cannot at the moment recall how to generate. If anyone cares
let me know and I'll find out.

Regards,
David B. Anderson davea@sgi.com http://reality.sgiweb.org/davea


             reply	other threads:[~2003-11-23 20:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-23 20:00 David Anderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=200311231959.hANJxOQs1070080@quasar.engr.sgi.com \
    --to=davea@quasar.engr.sgi.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