Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Stan Shebs <shebs@apple.com>, GDB <gdb@sourceware.cygnus.com>,
	binutils@sourceware.cygnus.com, linux-mips@oss.sgi.com
Subject: Re: stabs or ecoff for Linux/mips
Date: Thu, 07 Jun 2001 12:24:00 -0000	[thread overview]
Message-ID: <20010607122405.A16724@lucon.org> (raw)
In-Reply-To: <873d9cnmad.fsf@cgsoftware.com>

On Thu, Jun 07, 2001 at 03:05:14PM -0400, Daniel Berlin wrote:
> Stan Shebs <shebs@apple.com> writes:
> 
> > "H . J . Lu" wrote:
> >> 
> >> What is the better debug format for Linux/mips in the terms of gdb
> >> and binutils, stabs or ecoff? I know the future is dwarf2. But I need
> >> something stable now. Since Linux/x86 uses stabs, I lean toward to
> >> stabs. Any comments?
> > 
> > Go with stabs and ELF.  Neither ecoff's base file format nor the debug
> > info were particularly well-documented (I remember some of the bits in
> > GNU being figured out by reverse engineering!), perpetuating it will
> > just make your life more difficult in the long run.  It will also be
> > easier to move to dwarf2 when the opportunity arises.
> 
> mdebugread is also an evil piece of code. 

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


H.J.


  reply	other threads:[~2001-06-07 12:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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-11 11:25 Bob Zulawnik

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=20010607122405.A16724@lucon.org \
    --to=hjl@lucon.org \
    --cc=binutils@sourceware.cygnus.com \
    --cc=dan@cgsoftware.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=shebs@apple.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