From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7310 invoked by alias); 18 Nov 2005 01:19:57 -0000 Received: (qmail 7301 invoked by uid 22791); 18 Nov 2005 01:19:55 -0000 Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.192) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 18 Nov 2005 01:19:55 +0000 Received: by zproxy.gmail.com with SMTP id l1so75523nzf for ; Thu, 17 Nov 2005 17:19:53 -0800 (PST) Received: by 10.37.12.41 with SMTP id p41mr7307823nzi; Thu, 17 Nov 2005 17:19:53 -0800 (PST) Received: by 10.37.2.35 with HTTP; Thu, 17 Nov 2005 17:19:53 -0800 (PST) Message-ID: <8f2776cb0511171719k2ff35effqda392d272f97ab7@mail.gmail.com> Date: Fri, 18 Nov 2005 01:19:00 -0000 From: Jim Blandy To: teresa.rivas@cadenux.com Subject: Re: gdb debugging threads help Cc: gdb@sources.redhat.com In-Reply-To: <1132274170.32154.20.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1132274170.32154.20.camel@localhost.localdomain> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-11/txt/msg00365.txt.bz2 On 11/17/05, Teresa Rivas wrote: > I see there is a thread-db.o target on the gdb/Makefile file but I can't > configure gdb so it execute this thread-db.o target which I believe add > the gdb debbug thread support. I haven't used gdbserver much, but I can at least tell you not to worry about thread-db.o. That's not appropriate for cross-debugging configurations; it's only used for native debugging. That file acts as the interface between GDB and the libthread_db.so provided by the operating system; when cross-debugging, it's gdbserver that needs to link against the libthread_db.so, not GDB.