From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13258 invoked by alias); 11 Apr 2010 16:13:13 -0000 Received: (qmail 13248 invoked by uid 22791); 11 Apr 2010 16:13:12 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 11 Apr 2010 16:13:08 +0000 Received: (qmail 2470 invoked from network); 11 Apr 2010 16:13:06 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 11 Apr 2010 16:13:06 -0000 From: Pedro Alves To: "H.J. Lu" Subject: Re: Fix solib-disc.exp regression with x86 gdbserver Date: Sun, 11 Apr 2010 16:13:00 -0000 User-Agent: KMail/1.12.2 (Linux/2.6.31-20-generic; KDE/4.3.2; x86_64; ; ) Cc: gdb-patches@sourceware.org References: <201004110252.35997.pedro@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201004111713.04169.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-04/txt/msg00325.txt.bz2 On Sunday 11 April 2010 17:04:28, H.J. Lu wrote: > I got following extra failures with native gdbserver on Linux/x86-64. Compared to what? > Are they expected? > > FAIL: gdb.ada/tasks.exp: continue to breakpoint (the program exited) > FAIL: gdb.ada/tasks.exp: continue until end of program (the program is > no longer running) > FAIL: gdb.ada/tasks.exp: info tasks after hitting breakpoint > FAIL: gdb.ada/tasks.exp: info tasks before inserting breakpoint No clue. > FAIL: gdb.base/break-entry.exp: running to *0x4002e0 in runto I see this too (Linux/x86-64). > FAIL: gdb.base/randomize.exp: fixed addresses should match Expected, gdbserver doesn't support disabling randomization. > FAIL: gdb.base/recurse.exp: second instance watchpoint deleted when > leaving scope I don't see this one. > FAIL: gdb.base/watch-vfork.exp: Watchpoint triggers after vfork (sw) > (the program exited) Expected. > FAIL: gdb.cp/exception.exp: continue to second throw I see this too. > FAIL: gdb.mi/mi-var-cmd.exp: in-and-out-of-scope: in scope now I see this too. > FAIL: gdb.threads/attach-stopped.exp: threaded: attach2, exit leaves > process sleeping I don't see this one. May be a red herring -- gdbserver doesn't support what's being tested, IIRC. > FAIL: gdb.threads/execl.exp: continue across exec > FAIL: gdb.threads/fork-child-threads.exp: get to the spawned thread > (the program exited) > FAIL: gdb.threads/fork-child-threads.exp: next over fork > FAIL: gdb.threads/fork-child-threads.exp: two threads found Expected, gdbserver doesn't support following exec or fork events. > FAIL: gdb.trace/backtrace.exp: 1.13: trace in recursion: depth not equal to 3 > FAIL: gdb.trace/while-dyn.exp: 5.12: define ws Only recently (a couple of days) have the gdb.trace/ tests started running against gdbserver (it didn't support tracepoints before), but, none of these fails are expected on x86_64. The all pass for me. I'd like to understand them. What are the failures like? -- Pedro Alves