public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Taylor <dtaylor@emc.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: stabs and macro information
Date: Wed, 16 Apr 2003 19:21:00 -0000	[thread overview]
Message-ID: <200304161755.h3GHtuV10145@mailhub.lss.emc.com> (raw)
In-Reply-To: Your message of "Wed, 16 Apr 2003 13:27:04 EDT." <20030416172704.GB16947@nevyn.them.org>

> Date: Wed, 16 Apr 2003 13:27:04 -0400
> From: Daniel Jacobowitz <drow@mvista.com>
> 
> On Wed, Apr 16, 2003 at 11:58:19AM -0400, David Taylor wrote:
> > Currently, when invoked with -gdwarf-2 -g3, gcc will record macro
> > information in a .debug_macinfo elf section.  And when presented with
> > an executable containing macro information in a .debug_macinfo
> > section, gdb will make use of it.
> > 
> > Many companies, including EMC, still use stabs.  So...  it would be
> > nice if the same was true of stabs.
> 
> A more interesting question, to me, is why EMC still needs to use
> stabs.  They are an inferior debug format, extremely hard to parse or
> extend.

EMC does some processing of stabs via in house tools.  I'm told that
at one point before I started here that they switched to dwarf for a
bit.  And that the dwarf that was generated by GCC (and hence had to
be handled by the local tools) changed a few times...  They got tired
of having to modify the in house tools, so they switched back to
stabs.

>          GCC's and GDB's current implementations of DWARF-2 (and 3) are
> somewhat lacking, but it's all fixable.

I imagine we will eventually switch.  But, as long as the gcc and gdb
dwarf implementations are perceived as 'somewhat lacking', it's harder
to make the case to management.

  reply	other threads:[~2003-04-16 17:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16 16:37 David Taylor
2003-04-16 17:12 ` Daniel Berlin
2003-04-16 17:27   ` David Taylor
2003-04-16 17:52     ` Daniel Jacobowitz
2003-04-16 18:44     ` Andrew Cagney
2003-04-16 18:09 ` Daniel Jacobowitz
2003-04-16 19:21   ` David Taylor [this message]
2003-04-16 21:18   ` Daniel Berlin
2003-04-17 16:58     ` David Taylor
2003-04-17 17:17       ` Daniel Jacobowitz
2003-04-24  6:21 ` Jim Blandy

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=200304161755.h3GHtuV10145@mailhub.lss.emc.com \
    --to=dtaylor@emc.com \
    --cc=drow@mvista.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).