From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFA: tolerate unavailable struct return values
Date: Thu, 29 Nov 2001 14:37:00 -0000 [thread overview]
Message-ID: <20011129173644.A15429@nevyn.them.org> (raw)
In-Reply-To: <20011129220913.2D72A5E9D8@zwingli.cygnus.com>
On Thu, Nov 29, 2001 at 05:09:13PM -0500, Jim Blandy wrote:
>
> On some architectures, it's impossible for GDB to find structs
> returned by value. These shouldn't be failures. Should they be
> passes?
Out of curiousity, which architectures? And to be pedantic, I suspect
that it might be "not always possible" rather than actually impossible.
Nit-picking aside, I agree with Michael. This is the most appropriate
use for XFAIL, as opposed to some of the other things we use it for :)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFA: tolerate unavailable struct return values
Date: Tue, 20 Nov 2001 07:19:00 -0000 [thread overview]
Message-ID: <20011129173644.A15429@nevyn.them.org> (raw)
Message-ID: <20011120071900.sSsh1b5CmzVBJUb-WH7i7TnZY74i-xTVN93MhW6RMZg@z> (raw)
In-Reply-To: <20011129220913.2D72A5E9D8@zwingli.cygnus.com>
On Thu, Nov 29, 2001 at 05:09:13PM -0500, Jim Blandy wrote:
>
> On some architectures, it's impossible for GDB to find structs
> returned by value. These shouldn't be failures. Should they be
> passes?
Out of curiousity, which architectures? And to be pedantic, I suspect
that it might be "not always possible" rather than actually impossible.
Nit-picking aside, I agree with Michael. This is the most appropriate
use for XFAIL, as opposed to some of the other things we use it for :)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-11-29 14:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 20:48 Jim Blandy
2001-11-29 14:08 ` Jim Blandy
2001-11-29 14:19 ` Michael Snyder
2001-11-19 22:30 ` Michael Snyder
2001-11-29 14:37 ` Daniel Jacobowitz [this message]
2001-11-20 7:19 ` Daniel Jacobowitz
2001-11-30 12:48 ` Jim Blandy
2001-11-23 13:51 ` Jim Blandy
2001-11-30 13:33 ` Daniel Jacobowitz
2001-11-24 10:23 ` Daniel Jacobowitz
2001-11-30 13:51 ` Michael Snyder
2001-11-24 23:01 ` Michael Snyder
2001-12-12 11:27 ` Elena Zannoni
2001-12-17 15:09 ` Jim Blandy
2001-12-18 9:35 ` Elena Zannoni
[not found] ` <87667t2loj.fsf@creche.redhat.com>
2001-11-29 22:41 ` Jim Blandy
2001-11-21 8:07 ` Jim Blandy
2001-11-29 22:46 Jim Blandy
2001-11-21 13:10 ` 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=20011129173644.A15429@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@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