From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7668 invoked by alias); 21 Jan 2009 00:14:47 -0000 Received: (qmail 7659 invoked by uid 22791); 21 Jan 2009 00:14:46 -0000 X-SWARE-Spam-Status: No, hits=-1.8 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; Wed, 21 Jan 2009 00:14:43 +0000 Received: from spaceape13.eur.corp.google.com (spaceape13.eur.corp.google.com [172.28.16.147]) by smtp-out.google.com with ESMTP id n0L0EefY022079 for ; Tue, 20 Jan 2009 16:14:41 -0800 Received: from wf-out-1314.google.com (wfc25.prod.google.com [10.142.3.25]) by spaceape13.eur.corp.google.com with ESMTP id n0L0EEMB016724 for ; Tue, 20 Jan 2009 16:14:37 -0800 Received: by wf-out-1314.google.com with SMTP id 25so3874166wfc.14 for ; Tue, 20 Jan 2009 16:14:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.142.185.21 with SMTP id i21mr1277631wff.311.1232496876674; Tue, 20 Jan 2009 16:14:36 -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: Wed, 21 Jan 2009 00:14:00 -0000 Message-ID: <8ac60eac0901201614o57f3fea8x7cfe84e7c4b4f312@mail.gmail.com> Subject: Re: gdb doesn't show all threads, but gdbserver does From: Paul Pluzhnikov To: teawater Cc: "N. van Bolhuis" , 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/msg00127.txt.bz2 On Tue, Jan 20, 2009 at 4:05 PM, teawater wrote: > Really? > Why your gdbserver can be use? Is it static link? I think it works for OP because with gdbserver, the host GDB is doing symbol lookups, and the copy of target libpthread which host GDB uses has not been stripped. Cheers, -- Paul Pluzhnikov