From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: MI tests: tolerate prototypes
Date: Sun, 03 Feb 2002 15:01:00 -0000 [thread overview]
Message-ID: <20020203180133.C26302@nevyn.them.org> (raw)
In-Reply-To: <20020203210609.E5E035E9DE@zwingli.cygnus.com>
On Sun, Feb 03, 2002 at 04:06:09PM -0500, Jim Blandy wrote:
>
> Sun Feb 3 12:56:38 2002 Jim Blandy <jimb@seadog.cygnus.com>
>
> * mi-var-child.exp ("get children of struct_declarations", "get
> children of struct_declarations.s2.u2.u1s2", "get children of
> weird"): Tolerate argument types when they appear in function
> types. (Dwarf 2 includes prototype info; STABS does not.)
> * mi0-var-child.exp: Same.
Just out of curiousity... does the stabs information really not contain
this data, or are we just not recovering it? Could you give an
example?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-03 23:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 13:04 Jim Blandy
2002-02-03 15:01 ` Daniel Jacobowitz [this message]
2002-02-05 15:54 ` Jim Blandy
2002-02-05 17:21 ` Daniel Jacobowitz
2002-02-05 20:30 ` Jim Blandy
2002-02-05 21:48 ` Daniel Jacobowitz
2002-02-06 10:48 ` Jim Blandy
2002-02-06 16:14 ` Andrew Cagney
2002-02-06 16:24 ` Daniel Jacobowitz
2002-02-07 11:01 ` Jim Blandy
2002-02-07 12:27 ` Daniel Jacobowitz
2002-02-08 10:03 ` Jim Blandy
2002-02-08 5:16 ` function pointer stabs (was Re: RFA: MI tests: tolerate prototypes) Jason Merrill
2002-02-08 7:44 ` Daniel Jacobowitz
2002-02-08 11:37 ` Jim Blandy
2002-02-08 14:51 ` Jim Blandy
2002-02-09 12:15 ` Jim Blandy
2002-02-09 14:13 ` Daniel Jacobowitz
2002-02-03 16:29 ` RFA: MI tests: tolerate prototypes Andrew Cagney
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=20020203180133.C26302@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.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