Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Zulawnik <bob.zulawnik@cportcorp.com>
To: hjl@lucon.org
Cc: gdb@sourceware.cygnus.com, binutils@sourceware.cygnus.com,
	linux-mips@oss.sgi.com
Subject: Re: stabs or ecoff for Linux/mips
Date: Mon, 11 Jun 2001 11:25:00 -0000	[thread overview]
Message-ID: <3B250CF9.8C966EC9@cportcorp.com> (raw)

"H . J . Lu" wrote:

> That matches my own experiences. In case you haven't noticed, I
> have checked in patches to switch Linux/mips to stabs in ELF :-).

For what it's worth : stabs format cannot express certain types
of debug info that mdebug (used in ecoff) can. An example of
that is so-called PDRs (Procedure Description Records) - they
describe frame size, register masks etc.). Thus, in order to
obtain information about a function (e.g. when setting a
breakpoint at the entrance to a function), gdb has to resort to 
heuristics and read the function prolog, trying to figure out
what registers are saved where, when is the frame setup complete
etc. There are assumptions made in that gdb code  (e.g.
mips32_heuristic_proc_desc() and mips16_heuristic_proc_desc())
that have to match exactly what the compiler has done (as in
"the occurrence of instruction 'x' signifies this"). Thus,
using the stabs opens the debugger to potential misinterpretations
of the code generated by the compiler (e.g. when a new type
of frame is introduced, or maybe with some weird optimization).
I understand that there are other arguments for using stabs and 
that dwarf2 is the long-term goal, this is just an FYI. 

Bob Zulawnik


             reply	other threads:[~2001-06-11 11:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11 11:25 Bob Zulawnik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-07  9:33 H . J . Lu
2001-06-07 11:04 ` Andrew Cagney
2001-06-07 11:13   ` H . J . Lu
2001-06-07 11:20     ` Ian Lance Taylor
2001-06-07 11:27     ` Andrew Cagney
2001-06-07  9:31 H . J . Lu
2001-06-07  9:56 ` Daniel Berlin
2001-06-07 11:42 ` Stan Shebs
2001-06-07 12:05   ` Daniel Berlin
2001-06-07 12:24     ` H . J . Lu

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=3B250CF9.8C966EC9@cportcorp.com \
    --to=bob.zulawnik@cportcorp.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=hjl@lucon.org \
    --cc=linux-mips@oss.sgi.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