Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Michael Snyder <msnyder@cygnus.com>,
	Daniel Jacobowitz <drow@mvista.com>,
	<gdb-patches@sources.redhat.com>
Subject: Re: RFA: GCC stabs don't contain prototype info
Date: Fri, 16 Nov 2001 10:45:00 -0000	[thread overview]
Message-ID: <npwv0bh52k.fsf@zwingli.cygnus.com> (raw)
Message-ID: <20011116104500.K4uHQvdqEGovnp8jV2o5cogP32_9w0OwCBs9t_WDQvs@z> (raw)
In-Reply-To: Daniel Berlin's message of Tue, 27 Nov 2001 17:27:17 -0500 (EST)


Daniel Berlin <dan@cgsoftware.com> writes:
> > 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.

With Dwarf 2, GDB always has enough information to do the right
thing, but it doesn't use it.

At the moment, a function type can have its TYPE_FLAG_PROTOTYPED flag
set or clear.  Stabs doesn't set it reliably; Dwarf 2 does.  But the
code which checks this flag doesn't know where its setting came from,
so it doesn't know whether it should trust it or not.  There's an
arch-specific macro which says whether it should.  *gag*


  parent reply	other threads:[~2001-11-28  4:49 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
2001-11-27 14:27         ` Daniel Berlin
2001-11-27 20:49         ` Jim Blandy [this message]
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=npwv0bh52k.fsf@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=dan@cgsoftware.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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