From: Jan Vrany <jan.vrany@fit.cvut.cz>
To: gdb@sourceware.org
Subject: Re: MI / Python tests failing on my machine (x86_64)
Date: Mon, 10 Jul 2017 19:58:00 -0000 [thread overview]
Message-ID: <1499716698.3437.1.camel@fit.cvut.cz> (raw)
In-Reply-To: <830dcdc7-9162-d9e4-2f5b-ad6ea068c137@redhat.com>
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
next prev parent reply other threads:[~2017-07-10 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 6:42 Jan Vrany
2017-07-05 9:46 ` Phil Muldoon
2017-07-10 19:58 ` Jan Vrany [this message]
2017-07-11 15:19 ` Yao Qi
2017-07-12 14:21 ` Jan Vrany
2017-07-25 11:04 ` Yao Qi
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=1499716698.3437.1.camel@fit.cvut.cz \
--to=jan.vrany@fit.cvut.cz \
--cc=gdb@sourceware.org \
/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