From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17947 invoked by alias); 11 Apr 2010 16:18:42 -0000 Received: (qmail 17938 invoked by uid 22791); 11 Apr 2010 16:18:41 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG45 X-Spam-Check-By: sourceware.org Received: from mail-vw0-f41.google.com (HELO mail-vw0-f41.google.com) (209.85.212.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 11 Apr 2010 16:18:37 +0000 Received: by vws15 with SMTP id 15so1089003vws.0 for ; Sun, 11 Apr 2010 09:18:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.44.198 with HTTP; Sun, 11 Apr 2010 09:18:35 -0700 (PDT) In-Reply-To: <201004111713.04169.pedro@codesourcery.com> References: <201004110252.35997.pedro@codesourcery.com> <201004111713.04169.pedro@codesourcery.com> Date: Sun, 11 Apr 2010 16:18:00 -0000 Received: by 10.220.108.227 with SMTP id g35mr1355734vcp.184.1271002715287; Sun, 11 Apr 2010 09:18:35 -0700 (PDT) Message-ID: Subject: Re: Fix solib-disc.exp regression with x86 gdbserver From: "H.J. Lu" To: Pedro Alves Cc: gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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/msg00327.txt.bz2 On Sun, Apr 11, 2010 at 9:13 AM, Pedro Alves wrote: > 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? Compared to normal "make check". >> 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. =A0May 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. =A0The all pass > for me. =A0I'd like to understand them. =A0What are the failures like? > I am running Fedora 12. It may make a difference. BTW, I noticed a few bugs when running gdbserver tests on AVX. I will try to fix them. --=20 H.J.