From: Mark Kettenis <kettenis@gnu.org>
To: gdb@sources.redhat.com
Subject: Help, DejaGnu bails out on sigstep.exp
Date: Wed, 22 Sep 2004 21:15:00 -0000 [thread overview]
Message-ID: <200409222115.i8MLFPfB001254@elgar.sibelius.xs4all.nl> (raw)
This is what I get if I run
$ gmake RUNTESTFLAGS=gdb.base/sigstep.exp
on FreeBSD/amd64:
--------------------------------------------------
Test Run By kettenis on Wed Sep 22 23:03:33 2004
Native configuration is x86_64-unknown-freebsd5.2
=== gdb tests ===
Schedule of variations:
unix
Running target unix
Using ../../../src/gdb/testsuite/../../dejagnu/baseboards/unix.exp as board description file for target.
Using ../../../src/gdb/testsuite/../../dejagnu/config/unix.exp as generic interface file for target.
Using ../../../src/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file.
Running ../../../src/gdb/testsuite/gdb.base/sigstep.exp ...
ERROR: (DejaGnu) proc "other" does not exist.
The error code is NONE
The info on the error is:
close: invalid spawn id (6)
while executing
"close -i 6"
invoked from within
"catch "close -i $spawn_id""
=== gdb Summary ===
# of expected passes 23
/usr/home/kettenis/sandbox/gdb/obj/gdb/testsuite/../../gdb/gdb version 2004-09-22-cvs -nx
gmake: *** [just-check] Error 1
--------------------------------------------------
If I run this on OpenBSD/amd64 I get something similar:
--------------------------------------------------
Test Run By kettenis on Wed Sep 22 23:11:04 2004
Native configuration is x86_64-unknown-openbsd3.5
=== gdb tests ===
Schedule of variations:
unix
Running target unix
Using ../../../src/gdb/testsuite/../../dejagnu/baseboards/unix.exp as board description file for target.
Using ../../../src/gdb/testsuite/../../dejagnu/config/unix.exp as generic interface file for target.
Using ../../../src/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file.
Running ../../../src/gdb/testsuite/gdb.base/sigstep.exp ...
FAIL: gdb.base/sigstep.exp: step from handler; leave handler (timeout)
FAIL: gdb.base/sigstep.exp: stepi from handleri; leave signal trampoline
FAIL: gdb.base/sigstep.exp: next from handler; continue to handler
FAIL: gdb.base/sigstep.exp: nexti from handleri; leave signal trampoline
FAIL: gdb.base/sigstep.exp: finish from handleri; continue to handler
FAIL: gdb.base/sigstep.exp: finish from handleri; leave handler (in main)
FAIL: gdb.base/sigstep.exp: finish from handleri; leave signal trampoline
FAIL: gdb.base/sigstep.exp: return from handleri; continue to handler
ERROR: Undefined command "return".
ERROR: Got interactive prompt.
ERROR: breakpoints not deleted
ERROR: (DejaGnu) proc "other" does not exist.
The error code is NONE
=== gdb Summary ===
# of expected passes 12
# of unexpected failures 8
# of unresolved testcases 3
/home/kettenis/sandbox/gdb/obj/gdb/testsuite/../../gdb/gdb version 2004-09-22-cvs -nx
gmake: *** [just-check] Error 1
--------------------------------------------------
What's happening here? I don't understand it. It's pretty nasty
since for a normal "make check" this means that all the tests after
gdb.base/sigstep.exp don't run.
Mark
next reply other threads:[~2004-09-22 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 21:15 Mark Kettenis [this message]
2004-09-22 21:40 ` Andrew Cagney
2004-09-22 21:45 ` Michael Chastain
2004-09-23 18:51 ` Mark Kettenis
2004-09-23 20:01 ` Michael Chastain
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=200409222115.i8MLFPfB001254@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=gdb@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