From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3812 invoked by alias); 21 Jan 2009 10:32:25 -0000 Received: (qmail 3803 invoked by uid 22791); 21 Jan 2009 10:32:25 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-vbr3.xs4all.nl (HELO smtp-vbr3.xs4all.nl) (194.109.24.23) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 21 Jan 2009 10:32:17 +0000 Received: from mail3.aimsys.nl (a80-127-156-242.adsl.xs4all.nl [80.127.156.242]) by smtp-vbr3.xs4all.nl (8.13.8/8.13.8) with ESMTP id n0LAW78Y000128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jan 2009 11:32:09 +0100 (CET) (envelope-from nvbolhuis@aimvalley.nl) Received: from linpc062.aimsys.nl (linpc062.aimsys.nl [10.10.4.142]) (authenticated bits=0) by mail3.aimsys.nl (8.14.2/8.14.2) with ESMTP id n0LAW3eG030658; Wed, 21 Jan 2009 11:32:04 +0100 Message-ID: <4976F9A3.7060307@aimvalley.nl> Date: Wed, 21 Jan 2009 10:32:00 -0000 From: Norbert van Bolhuis User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Paul Pluzhnikov CC: Andreas Schwab , teawater , gdb@sourceware.org Subject: Re: gdb doesn't show all threads, but gdbserver does References: <4974EBFF.307@aimvalley.nl> <49757D1C.7010309@aimvalley.nl> <8ac60eac0901201037t71b6bd62j8668bd004e933f53@mail.gmail.com> <49763169.8070208@aimvalley.nl> <8ac60eac0901201236i2d3a266akaa673cd12a4ec7cb@mail.gmail.com> <49763F67.5010009@aimvalley.nl> <8ac60eac0901201445m4d85d30k5b5fc87783208a32@mail.gmail.com> In-Reply-To: <8ac60eac0901201445m4d85d30k5b5fc87783208a32@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 X-SW-Source: 2009-01/txt/msg00136.txt.bz2 Paul Pluzhnikov wrote: > On Tue, Jan 20, 2009 at 2:24 PM, Andreas Schwab wrote: > >> It's actually libthread_db that needs a non-global symbol from >> libpthread. > > IOW, it's a glibc feature :) > > Stripping libpthread appears to be a very common mistake: > > - we've seen it twice on this list in the last two weeks, > - I made it myself 4 weeks ago, even though I *knew* that libpthread > must not be stripped. > > I wonder if we should warn glibc users? Something like: > > Warning: your /lib64/libpthread.so.0 has been stripped. > GDB will not see other threads, and multithreaded debugging will > be unreliable. > See http://sourceware.org/gdb/wiki/... for further info. > I consulted the GDB manual first, then google. http://sourceware.org/gdb/wiki is an interesting source of information. I expect to see this common mistake being mentioned there, but I can't find it. Anyway, thanks to everybody for all answers.