From: Corinna Vinschen <vinschen@redhat.com>
To: gdb@sources.redhat.com
Subject: MI testsuite question
Date: Tue, 25 Mar 2003 16:44:00 -0000 [thread overview]
Message-ID: <20030325164353.GI23762@cygbert.vinschen.de> (raw)
Hi,
while running the xstormy16 testsuite I came across a bunch of FAILs
which I don't know how to solve correctly:
WARNING: Using CLI jump command, expect run-to-main FAIL
jump *_start^M
&"jump *_start\n"^M
^done,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x000080ea",func="main",args=[{name="argc",value="0"},{name="argv",value="0x0"}],file="/home/corinna/src/gdb/testsuite/gdb.mi/gdb701.c",line="13"}^M
(gdb) ^M
FAIL: gdb.mi/gdb701.exp: mi runto main (2)
As you can see, the returned string begins with
"^done,"
while the testsuite (here proc mi_runto in lib/mi-support.exp) expects
".*000\\*stopped,"
Everything else is ok. So, is the testsuite wrong or is gdb misbehaving?
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:vinschen@redhat.com
next reply other threads:[~2003-03-25 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 16:44 Corinna Vinschen [this message]
2003-03-25 16:58 ` 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=20030325164353.GI23762@cygbert.vinschen.de \
--to=vinschen@redhat.com \
--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