From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26678 invoked by alias); 26 Feb 2010 09:04:55 -0000 Received: (qmail 26577 invoked by uid 22791); 26 Feb 2010 09:04:54 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp.telit.com (HELO smtp.telit.com) (88.37.127.140) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 26 Feb 2010 09:04:46 +0000 Received: from urano.tmt.telital.com (urano.telital.com [172.21.1.104]) by smtp.telit.com (8.14.1/8.13.8) with ESMTP id o1Q94Keo024394; Fri, 26 Feb 2010 10:04:20 +0100 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: "Disabling thread support in gdbserver" problem Date: Fri, 26 Feb 2010 09:04:00 -0000 Message-ID: In-Reply-To: <201002251949.56189.yann.morin.1998@anciens.enib.fr> From: "Daniele Palmas" To: "Yann E. MORIN" , X-Telit-MailScanner-Information: Please contact the ISP for more information X-Telit-MailScanner: Found to be clean X-Telit-MailScanner-From: daniele.palmas@telit.com X-IsSubscribed: yes Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2010-02/txt/msg00083.txt.bz2 -----Original Message----- From: Yann E. MORIN [mailto:yann.morin.1998@anciens.enib.fr]=20 Sent: gioved=EC 25 febbraio 2010 19.50 To: crossgcc@sourceware.org Cc: Daniele Palmas Subject: Re: "Disabling thread support in gdbserver" problem >> Building the toolchain succeeded correctly, but analyzing the log I've f= ound >> the following lines:=20 >> [--SNIP--] >> [INFO ]=A0 Installing gdbserver >> [EXTRA]=A0=A0=A0 Configuring gdbserver >> [WARN ]=A0=A0=A0 configure: WARNING: Could not find libthread_db. >> [WARN ]=A0=A0=A0 configure: WARNING: Disabling thread support in gdbserv= er. >> [--SNIP--] >> Any hint? > Well, I was really sckeptical about this issue, and while I was trying > to solve it, I noticed that I do not have the issue! My gdbserver is > statically built, and properly finds the static version of libthread_db. > > If you manage to somehow understand why it fails on your side, I would be > glad to hear about it, so we can try and fix it. > > Regards, > Yann E. MORIN. I'll try to take a look into that. Please also note that the gdbserver built with gdb 6.8 doesn't work with my= target (ptrace error when debugging threads that stops the debugger). I had to compile separately from crosstool-NG the gdb and gdbserver 7.0 for= being able to debug threads. Regards, Daniele -- For unsubscribe information see http://sourceware.org/lists.html#faq