From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa:testsuite} Overhaul sizeof.exp
Date: Wed, 20 Feb 2002 06:57:00 -0000 [thread overview]
Message-ID: <3C73B949.90209@cygnus.com> (raw)
In-Reply-To: <200202200456.g1K4uwX27098@duracef.shout.net>
> Hi Andrew,
>
>
>> Unfortunatly it doesn't address the x86 problem. Looking at
>> printcmd.c:print_scalar_formatted() the function behaves differently
>> when sizeof (host LONGEST) < sizeof (target type) (i.e. x86) :-( I
>> think this a very long standing bug.
>>
>> The problem I guess is what to do short term with this part of the test.
>
>
> My opinion is that if a test finds a bug, it is a good test. A really
> great test causes the machine to reboot, catch on fire, and install
> Windows XP from a Russian warez mirror.
>
> Here is some policy from gcc:
>
> http://gcc.gnu.org/bugs.html#manage
Yes. I poked a finger in that pie recently by getting approval to
commit a test that demonstrated a regression! (Wswitch.c)
The XFAIL policy is different to GDB. GDB interprets XFAILs to mean not
supported due to something outside of GDB's control. Not this is a bug
but we're not fixing it at present.
Anyway, what we're looking at here isn't a regression - it is just wierd.
> I think this would be a good policy for gdb. What do you think?
>
> I will re-run my test bed on the new patch shortly.
>
> Michael C
I had a bit of a think. I'm going to change the test so that it avoids
the /d problem. I figure I'm trying to test GDB vs TARGET sizes, not
printf. I'll bug report the above problem.
Patch shortly.
Andrew
next prev parent reply other threads:[~2002-02-20 14:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 20:57 Michael Elizabeth Chastain
2002-02-20 6:57 ` Andrew Cagney [this message]
2002-02-20 7:21 ` Andrew Cagney
2002-02-20 8:19 ` Fernando Nasser
2002-02-20 17:57 ` Andrew Cagney
2002-02-20 8:16 ` Fernando Nasser
2002-02-20 8:51 ` Daniel Jacobowitz
2002-02-20 9:24 ` Fernando Nasser
2002-02-21 14:04 ` Jim Blandy
2002-02-21 14:23 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-02-20 10:24 Michael Elizabeth Chastain
2002-02-20 11:48 ` Fernando Nasser
2002-02-20 9:49 Michael Elizabeth Chastain
2002-02-20 10:06 ` Fernando Nasser
2002-02-20 10:12 ` Daniel Jacobowitz
2002-02-20 10:07 ` Daniel Jacobowitz
2002-02-20 10:18 ` Fernando Nasser
2002-02-20 10:07 ` Richard Earnshaw
2002-02-20 9:17 Michael Elizabeth Chastain
2002-02-20 9:42 ` Fernando Nasser
2002-02-20 10:20 ` Andrew Cagney
2002-02-20 8:59 Michael Elizabeth Chastain
2002-02-19 20:43 Michael Elizabeth Chastain
2002-02-21 14:03 ` Jim Blandy
2002-02-19 15:46 Michael Elizabeth Chastain
2002-02-19 18:19 ` Andrew Cagney
2002-02-19 15:17 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=3C73B949.90209@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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