MI testsuite question

MI testsuite question

[Corinna Vinschen]

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

Re: MI testsuite question

[Andrew Cagney]

> 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

This warning is refering to ...

>   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)

this failure.

> 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?

It is a known bug in gdb.

Andrew