Re: MI / Python tests failing on my machine (x86_64)

Jan Vrany <[email protected]>
Newsgroups gmane.comp.gdb.devel
Message-ID <[email protected]> 
On Wed, 2017-07-05 at 10:46 +0100, Phil Muldoon wrote:
> On 05/07/17 07:42, Jan Vrany wrote:
> > Hi there, 
> > 
> > I'm experimenting with Didier Nadeau's patches for python-defined
> > MI commands [1]
> > 
> > I tried to compile recent gdb (25c5412713ba) and then run MI and
> > python
> > tests to ensure all is OK before I start hacking. 
> > 
> > I run these tests using:
> > 
> > make check RUNTESTFLAGS='TRANSCRIPT=y gdb.mi/*.exp
> > gdb.python/*.exp' 
> > 
> > but 58 tests seems to fail: 
> > 
> > # of expected passes		4810
> > # of unexpected failures	58
> > # of expected failures		9
> > # of known failures		13
> > # of untested testcases		3
> > # of unsupported tests		1
> 
> I don't see this from HEAD.
> 
> > 
> > For GDB 8.0.0 (1f1c02597cc1) test results are the same on my
> > machine.
> > I compiled gdb on Linux (Debian Jessie if that matters) using
> > simple
> > 
> >    ./configure && make
> > 
> > Is that expected? Do I need to perform some additional setup to run
> > tests? 
> 
> What tests fail and why? It's difficult to work out what is going
> on without some trail to follow.

Sure. Following fails: 

gdb.mi/mi-break.exp
gdb.mi/mi2-amd64-entry-value.exp
gdb.mi/mi-var-cmd.exp
gdb.mi/mi-var-invalidate.exp

more details: 

~/Projects/gdb/sources1/gdb/testsuite$ egrep ^FAIL gdb.sum
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint at main
(unexpected output)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=main: mi runto main (unknown
output after running)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint commands:
insert breakpoint at basics.c:callee2, again (unexpected output)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint commands:
set commands (unexpected output)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=main: breakpoint commands:
continue (MI error)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=main: intermediate stop and
continue, bp commands
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=main: intermediate stop and
continue, mi running
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=main: test hitting
breakpoint with commands (timeout)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=main: break-insert -a
operation (unexpected output)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=main: eval tpnum after
tracepoint (unexpected output)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=separate: breakpoint at main
(unexpected output)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=separate: mi runto main
(unknown output after running)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=separate: breakpoint
commands: insert breakpoint at basics.c:callee2, again (unexpected
output)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=separate: breakpoint
commands: set commands (unexpected output)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=separate: breakpoint
commands: continue (MI error)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=separate: intermediate stop
and continue, bp commands
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=separate: intermediate stop
and continue, mi running
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=separate: test hitting
breakpoint with commands (timeout)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=separate: break-insert -a
operation (unexpected output)
gdb.sum:FAIL: gdb.mi/mi-break.exp: mi-mode=separate: eval tpnum after
tracepoint (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: only: entry_equal: stop
(stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: only: entry_equal:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: only: entry_different:
stop (stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: only: entry_different:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: only: validity: stop
(stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: only: validity: -stack-
list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: preferred: entry_equal:
stop (stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: preferred: entry_equal:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: preferred:
entry_different: stop (stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: preferred:
entry_different: -stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: preferred: validity:
stop (stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: preferred: validity:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: if-needed: validity:
stop (stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: if-needed: validity:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: both: entry_equal: stop
(stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: both: entry_equal:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: both: entry_different:
stop (stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: both: entry_different:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: both: validity: stop
(stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: both: validity: -stack-
list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: compact: entry_equal:
stop (stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: compact: entry_equal:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: compact:
entry_different: stop (stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: compact:
entry_different: -stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: compact: validity: stop
(stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: compact: validity:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: default: entry_equal:
stop (stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: default: entry_equal:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: default:
entry_different: stop (stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: default:
entry_different: -stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: default: validity: stop
(stopped at wrong place)
gdb.sum:FAIL: gdb.mi/mi2-amd64-entry-value.exp: default: validity:
-stack-list-variables (unexpected output)
gdb.sum:FAIL: gdb.mi/mi-var-cmd.exp: run to var-cmd.c:367 (set
breakpoint) (unexpected output)
gdb.sum:FAIL: gdb.mi/mi-var-cmd.exp: wait for stop (frozen: step to
367)
gdb.sum:FAIL: gdb.mi/mi-var-cmd.exp: frozen: go to line 367
gdb.sum:FAIL: gdb.mi/mi-var-cmd.exp: frozen: step over 367 (MI error)
gdb.sum:FAIL: gdb.mi/mi-var-invalidate.exp: breakpoint at main
(unexpected output)
gdb.sum:FAIL: gdb.mi/mi-var-invalidate.exp: mi runto main (unknown
output after running)

When I look closer at gdb.mi/mi-var-cmd.exp, the first failure is
because gdb fails to insert a breakpoint: 

...
PASS: gdb.mi/mi-var-cmd.exp: delete array_ptr
Expecting: ^(-break-insert -t var-cmd\.c:367[
]+)?(\^done,bkpt=.*[
]+[(]gdb[)] 
[ ]*)
-break-insert -t var-cmd.c:367
^error,msg="Cannot access memory at address 0xde7"
(gdb) 
...

But when I try to do it manually, it looks it does set the breakpoint
just fine.

Jan



> 
> Cheers
> 
> Phil
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.