From: Daniel Berlin <dan@cgsoftware.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: Jim Blandy <jimb@cygnus.com>, Daniel Jacobowitz <drow@mvista.com>,
<gdb-patches@sources.redhat.com>
Subject: Re: RFA: GCC stabs don't contain prototype info
Date: Tue, 27 Nov 2001 14:27:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0111271725220.20943-100000@www.cgsoftware.com> (raw)
Message-ID: <20011127142700.N-XNrjASt95s062aDKHoxPkheuS2O5I-LJRlhL8dtAs@z> (raw)
In-Reply-To: <3C0410D8.58D8D0FB@cygnus.com>
On Tue, 27 Nov 2001, Michael Snyder wrote:
> Jim Blandy wrote:
> >
> > Daniel Jacobowitz <drow@mvista.com> writes:
> > > Is there a standard stabs convention for this? If so, it would be a
> > > good idea to make development GCC emit it.
> >
> > Yes, there's the encoding developed by Sun, described in the GNU stabs
> > manual. It looks to me like GDB is ready to consume this info, so
> > getting GCC to emit it would be great.
> >
> > Until that's done, however, this test should XFAIL, so other engineers
> > won't waste their time re-analyzing the failure. (I don't mean to
> > imply that you disagree; I just want to make things clear to the test
> > suite maintainers.)
>
> FYI, it is not only stabs that fails this test. I've got a recent
> elf/dwarf target that also fails it.
Err, it shouldn't.
Unless you really mean dwarf and not dwarf2.
GCC adds DW_AT_prototyped to prototyped functions.
And gdb consumes it.
> The problem wherein GDB cannot
> reliably make this distinction is long standing, and much discussed
> in the past. Unfortunately most of the people who have taken part
> in this discussion aren't around any more.
>
next prev parent reply other threads:[~2001-11-27 14:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 19:43 Jim Blandy
2001-11-13 10:56 ` Jim Blandy
2001-11-26 19:47 ` Daniel Jacobowitz
2001-11-13 11:07 ` Daniel Jacobowitz
2001-11-26 20:19 ` Jim Blandy
2001-11-13 15:38 ` Jim Blandy
2001-11-27 14:16 ` Michael Snyder
2001-11-15 7:01 ` Michael Snyder
2001-11-15 8:00 ` Daniel Berlin [this message]
2001-11-27 14:27 ` Daniel Berlin
2001-11-27 20:49 ` Jim Blandy
2001-11-16 10:45 ` Jim Blandy
2001-11-27 14:10 ` Michael Snyder
2001-11-15 2:38 ` Michael Snyder
2001-12-07 13:17 ` 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=Pine.LNX.4.33.0111271725220.20943-100000@www.cgsoftware.com \
--to=dan@cgsoftware.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.com \
--cc=msnyder@cygnus.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