* MI / Python tests failing on my machine (x86_64)
@ 2017-07-05 6:42 Jan Vrany
2017-07-05 9:46 ` Phil Muldoon
0 siblings, 1 reply; 6+ messages in thread
From: Jan Vrany @ 2017-07-05 6:42 UTC (permalink / raw)
To: gdb
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
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?
Thanks, Jan
[1]: https://sourceware.org/ml/gdb/2017-06/msg00010.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MI / Python tests failing on my machine (x86_64)
2017-07-05 6:42 MI / Python tests failing on my machine (x86_64) Jan Vrany
@ 2017-07-05 9:46 ` Phil Muldoon
2017-07-10 19:58 ` Jan Vrany
0 siblings, 1 reply; 6+ messages in thread
From: Phil Muldoon @ 2017-07-05 9:46 UTC (permalink / raw)
To: Jan Vrany, gdb
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.
Cheers
Phil
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MI / Python tests failing on my machine (x86_64)
2017-07-05 9:46 ` Phil Muldoon
@ 2017-07-10 19:58 ` Jan Vrany
2017-07-11 15:19 ` Yao Qi
0 siblings, 1 reply; 6+ messages in thread
From: Jan Vrany @ 2017-07-10 19:58 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MI / Python tests failing on my machine (x86_64)
2017-07-10 19:58 ` Jan Vrany
@ 2017-07-11 15:19 ` Yao Qi
2017-07-12 14:21 ` Jan Vrany
0 siblings, 1 reply; 6+ messages in thread
From: Yao Qi @ 2017-07-11 15:19 UTC (permalink / raw)
To: Jan Vrany; +Cc: gdb
Jan Vrany <jan.vrany@fit.cvut.cz> writes:
> 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)
> ...
Are you running tests on debian? It is probably caused by this bug
https://sourceware.org/bugzilla/show_bug.cgi?id=21555 I am fixing this.
I can reproduce your fail this way,
$ make check RUNTESTFLAGS="CFLAGS_FOR_TARGET='-fPIE -pie' mi-break.exp"
--
Yao (齐尧)
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: MI / Python tests failing on my machine (x86_64)
2017-07-11 15:19 ` Yao Qi
@ 2017-07-12 14:21 ` Jan Vrany
2017-07-25 11:04 ` Yao Qi
0 siblings, 1 reply; 6+ messages in thread
From: Jan Vrany @ 2017-07-12 14:21 UTC (permalink / raw)
To: Yao Qi; +Cc: gdb
On Tue, 2017-07-11 at 16:19 +0100, Yao Qi wrote:
> Jan Vrany <jan.vrany@fit.cvut.cz> writes:
>
> > 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)Â
> > ...
>
> Are you running tests on debian?  It is probably caused by this bug
> https://sourceware.org/bugzilla/show_bug.cgi?id=21555Â Â I am fixing
> this.
Yes, I'm on debian. This looks likely!
I'll try on some other, non-PIE distro in next
couple weeks (I'm traveling now so I'm left with
my laptop only).
Thanks!
Jan
>
> I can reproduce your fail this way,
>
> $ make check RUNTESTFLAGS="CFLAGS_FOR_TARGET='-fPIE -pie' mi-
> break.exp"
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-07-25 11:04 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-07-05 6:42 MI / Python tests failing on my machine (x86_64) Jan Vrany
2017-07-05 9:46 ` Phil Muldoon
2017-07-10 19:58 ` Jan Vrany
2017-07-11 15:19 ` Yao Qi
2017-07-12 14:21 ` Jan Vrany
2017-07-25 11:04 ` Yao Qi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox