From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15541 invoked by alias); 16 Jul 2009 02:29:55 -0000 Received: (qmail 15528 invoked by uid 22791); 16 Jul 2009 02:29:55 -0000 X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_51,J_CHICKENPOX_81,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Jul 2009 02:29:46 +0000 Received: from zps75.corp.google.com (zps75.corp.google.com [172.25.146.75]) by smtp-out.google.com with ESMTP id n6G2Tfu8027052 for ; Thu, 16 Jul 2009 03:29:42 +0100 Received: from fxm6 (fxm6.prod.google.com [10.184.13.6]) by zps75.corp.google.com with ESMTP id n6G2TcPj029892 for ; Wed, 15 Jul 2009 19:29:39 -0700 Received: by fxm6 with SMTP id 6so3613572fxm.24 for ; Wed, 15 Jul 2009 19:29:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.49.12 with SMTP id b12mr4501993muk.51.1247711378290; Wed, 15 Jul 2009 19:29:38 -0700 (PDT) In-Reply-To: References: <20090605222214.66E2976BC4@localhost> <8ac60eac0906151139w23c6cc2ag9307d73232753f65@mail.gmail.com> <8ac60eac0906220910p5750f455u1e3dc462035d50b6@mail.gmail.com> <4A3FC8CA.5070700@vmware.com> <8ac60eac0906221321r45c43a13g87a830f8dd3487ea@mail.gmail.com> Date: Thu, 16 Jul 2009 02:43:00 -0000 Message-ID: Subject: Re: [patch] Fix for gdb.threads/staticthreads.exp failure on Linux From: Doug Evans To: Paul Pluzhnikov Cc: Michael Snyder , "gdb-patches@sourceware.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true 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: 2009-07/txt/msg00403.txt.bz2 On Wed, Jul 15, 2009 at 6:25 PM, Doug Evans wrote: > Running the testcase with --target_board=3Dnative-gdbserver doesn't have > this problem. =A0Some research as to what gdbserver is doing would be > illuminating. =A0"consistency is good": can you research what's > happening in gdbserver that it works there, and see if it's reasonable > to do the same thing in gdb? I spoke too soon. gdbserver does have the same problem, I just needed to look at gdb.log to see it. Process /usr/local/g3/gnu/sourceware/static-threads/build/obj32/gdb/testsui= te/gdb.threads/staticthreads created; pid =3D 19691^M Listening on port 2347^M target remote localhost:2347^M Remote debugging using localhost:2347^M Remote debugging from host 127.0.0.1^M Cannot get thread handle for LWP 19691: generic error^M _start () at ../sysdeps/i386/elf/start.S:65^M 65 xorl %ebp, %ebp^M (gdb) Cannot get thread handle for LWP 19691: generic error^M continue^M Continuing.^M ^M Breakpoint 1, main (argc=3D, argv=3D) at ../../../../src/gdb/testsuite/gdb.threads/staticthreads.c:51^M 51 pthread_attr_init (&attr);^M Current language: auto; currently c^M (gdb) PASS: gdb.threads/staticthreads.exp: rerun to main [The "value optimized out" seems like a bug, but a different bug. :-)]