From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Interesting PASS in gdb.log for mips-irix...
Date: Sun, 01 Aug 2004 19:23:00 -0000 [thread overview]
Message-ID: <410D4315.1060700@gnu.org> (raw)
In-Reply-To: <20040731212508.GF1167@gnat.com>
> I'm really overwhelmed right now with tons of different things to look
> at, all at the same time. I'll keep this in my list, but if somebody
> is interested, I'll be grateful.
(tha's what bug reports are for :-)
> The gdb.log file contains an entry like this:
>
> call Fun(foo)
> That operation is not available on integers of more than 8 bytes.
> (gdb) PASS: gdb.base/call-sc.exp: call Fun(foo); call call-sc-tld
>
> We got an error and yet we PASS. ?!?.
Here's the pair:
gdb_test "call Fun(foo)" "" "call Fun(foo); ${tests}"
gdb_test "p/c L" " = 49 '1'" "p/c L; ${tests}"
the second should still fail (the first could use gdb_test_exact I guess?).
Andrew
prev parent reply other threads:[~2004-08-01 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-31 21:25 Joel Brobecker
2004-08-01 19:23 ` Andrew Cagney [this message]
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=410D4315.1060700@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.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