From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4790 invoked by alias); 20 Jan 2009 22:45:33 -0000 Received: (qmail 4782 invoked by uid 22791); 20 Jan 2009 22:45:33 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 20 Jan 2009 22:45:27 +0000 Received: from zps76.corp.google.com (zps76.corp.google.com [172.25.146.76]) by smtp-out.google.com with ESMTP id n0KMjPvI031097 for ; Tue, 20 Jan 2009 14:45:25 -0800 Received: from an-out-0708.google.com (anab6.prod.google.com [10.100.53.6]) by zps76.corp.google.com with ESMTP id n0KMjMZB005612 for ; Tue, 20 Jan 2009 14:45:23 -0800 Received: by an-out-0708.google.com with SMTP id b6so98012ana.40 for ; Tue, 20 Jan 2009 14:45:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.142.125.4 with SMTP id x4mr898059wfc.223.1232491522349; Tue, 20 Jan 2009 14:45:22 -0800 (PST) In-Reply-To: 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> Date: Tue, 20 Jan 2009 22:45:00 -0000 Message-ID: <8ac60eac0901201445m4d85d30k5b5fc87783208a32@mail.gmail.com> Subject: Re: gdb doesn't show all threads, but gdbserver does From: Paul Pluzhnikov To: Andreas Schwab Cc: "N. van Bolhuis" , teawater , gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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/msg00124.txt.bz2 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. -- Paul Pluzhnikov