From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 74153 invoked by alias); 10 Jul 2017 19:58:30 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 74118 invoked by uid 89); 10 Jul 2017 19:58:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=Projects, TRANSCRIPT, frozen, validity X-HELO: relay.fit.cvut.cz Received: from relay.fit.cvut.cz (HELO relay.fit.cvut.cz) (147.32.232.237) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 10 Jul 2017 19:58:27 +0000 Received: from imap.fit.cvut.cz (imap.fit.cvut.cz [IPv6:2001:718:2:2901:0:0:0:238] (may be forged)) by relay.fit.cvut.cz (8.15.2/8.15.2) with ESMTPS id v6AJwJxv083059 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK) for ; Mon, 10 Jul 2017 21:58:19 +0200 (CEST) (envelope-from jan.vrany@fit.cvut.cz) Received: from sao (ip-62-24-85-77.net.upcbroadband.cz [62.24.85.77]) (authenticated bits=0 as user vranyj1) by imap.fit.cvut.cz (8.15.2/8.15.2) with ESMTPSA id v6AJwILj097048 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Mon, 10 Jul 2017 21:58:18 +0200 (CEST) (envelope-from jan.vrany@fit.cvut.cz) Message-ID: <1499716698.3437.1.camel@fit.cvut.cz> Subject: Re: MI / Python tests failing on my machine (x86_64) From: Jan Vrany To: gdb@sourceware.org Date: Mon, 10 Jul 2017 19:58:00 -0000 In-Reply-To: <830dcdc7-9162-d9e4-2f5b-ad6ea068c137@redhat.com> References: <1499236932.24598.1.camel@fit.cvut.cz> <830dcdc7-9162-d9e4-2f5b-ad6ea068c137@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-FIT-MailScanner-ID: v6AJwJxv083059 X-FIT-MailScanner: Found to be clean X-FIT-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=1.01, required 7, MISSING_FROM 1.00, RP_MATCHES_RCVD 0.01) X-FIT-MailScanner-SpamScore: s X-FIT-MailScanner-From: jan.vrany@fit.cvut.cz X-FIT-MailScanner-Watermark: 1500321501.43415@2LaAr4ZxI45zP6fYIdm8Mw X-IsSubscribed: yes X-SW-Source: 2017-07/txt/msg00015.txt.bz2 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