From: Mark Kettenis <kettenis@chello.nl>
To: brobecker@gnat.com
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com,
guitton.at.act-europe.dot.fr@elgar.kettenis.dyndns.org
Subject: Re: [patch] Test scalar call/return/finish test - call-sc
Date: Sun, 25 Apr 2004 11:44:00 -0000 [thread overview]
Message-ID: <200404251144.i3PBiaB6019886@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <20040424182018.GN2811@gnat.com> (message from Joel Brobecker on Sat, 24 Apr 2004 11:20:18 -0700)
Date: Sat, 24 Apr 2004 11:20:18 -0700
From: Joel Brobecker <brobecker@gnat.com>
> Joel, Jerome, AIX should have zero call-sc and structs failures (as
> there is for PPC/elf).
>
> committed,
> Andrew
> 2004-04-23 Andrew Cagney <cagney@redhat.com>
>
> * gdb.base/call-sc.exp: New test of scalar call/return values.
> * gdb.base/call-sc.c: Ditto.
The following FAILs seem to be caused by a problem in the test itself rather
than GDB.
FAIL: gdb.base/call-sc.exp: ptype foo; call-sc-tc cha
FAIL: gdb.base/call-sc.exp: ptype foo; call-sc-ts sho
FAIL: gdb.base/call-sc.exp: ptype foo; call-sc-ti i
FAIL: gdb.base/call-sc.exp: ptype foo; call-sc-tl lo
FAIL: gdb.base/call-sc.exp: ptype foo; call-sc-tll lo
FAIL: gdb.base/call-sc.exp: ptype foo; call-sc-tf float
FAIL: gdb.base/call-sc.exp: ptype foo; call-sc-td double
FAIL: gdb.base/call-sc.exp: ptype foo; call-sc-tld lo
FAIL: gdb.base/call-sc.exp: ptype foo; call-sc-te e
I agree. Seems to be a problem with the regexp that Andrew used.
Note that the types are truncated at the letter `n' ot `r'. The
attached patch works fixes these failures for me.
The following ones seem to be bona fide problems:
FAIL: gdb.base/call-sc.exp: value foo returned; return call-sc-tc
FAIL: gdb.base/call-sc.exp: value foo returned; return call-sc-ts
...
FAIL: gdb.base/call-sc.exp: p/c L; call call-sc-tf
I just checked in a patch that might fix these:
http://sources.redhat.com/ml/gdb-patches/2004-04/msg00608.html
Anyway, can anybody shoot any holes in my new regexp?
Mark
Index: testsuite/ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* gdb.base/call-sc.exp (start_scalars_test): Fix regular
expression that checks the return type.
Index: testsuite/gdb.base/call-sc.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/call-sc.exp,v
retrieving revision 1.1
diff -u -p -r1.1 call-sc.exp
--- testsuite/gdb.base/call-sc.exp 23 Apr 2004 23:34:53 -0000 1.1
+++ testsuite/gdb.base/call-sc.exp 25 Apr 2004 11:39:19 -0000
@@ -115,7 +115,7 @@ proc start_scalars_test { type } {
set test "ptype; ${testfile}"
set foo_t "xxx"
gdb_test_multiple "ptype ${type}" "${test}" {
- -re "type = (\[^\\r\\n\]*).*$gdb_prompt $" {
+ -re "type = (.*)\r\n.*$gdb_prompt $" {
set foo_t "$expect_out(1,string)"
pass "$test (${foo_t})"
}
next prev parent reply other threads:[~2004-04-25 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 0:03 Andrew Cagney
2004-04-24 18:20 ` Joel Brobecker
2004-04-25 11:44 ` Mark Kettenis [this message]
2004-04-25 14:27 ` Daniel Jacobowitz
2004-04-26 0:53 ` Joel Brobecker
2004-04-28 0:16 ` Mark Kettenis
2004-04-28 15:49 ` 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=200404251144.i3PBiaB6019886@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=guitton.at.act-europe.dot.fr@elgar.kettenis.dyndns.org \
/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