From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5858 invoked by alias); 8 Jan 2004 16:26:11 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 5850 invoked from network); 8 Jan 2004 16:26:11 -0000 Received: from unknown (HELO iua-mail.upf.es) (193.145.55.10) by sources.redhat.com with SMTP; 8 Jan 2004 16:26:11 -0000 Received: from iua-mail.upf.es ([193.145.55.10]) by iua-mail.upf.es with esmtp (Exim 3.35 #1 (Debian)) id 1AedH6-0000Os-00; Thu, 08 Jan 2004 17:44:48 +0100 Date: Thu, 08 Jan 2004 16:26:00 -0000 From: Maarten de Boer X-X-Sender: mdeboer@iua-mail.upf.es To: bug-glibc@gnu.org, , Subject: Re: gdb problem with kernel 2.6.0 and pthreads In-Reply-To: <20040107174932.7d7b9542.mdeboer@iua.upf.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact postmaster@iua.upf.es for more information X-MTG-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-5.801, required 5, BAYES_10) X-SW-Source: 2004-01/txt/msg00088.txt.bz2 As suggested by several people, moving to gdb 6.0 solves the problem, so for the record. Thanks, Maarten > Hello, > > Sorry for cross-posting, but I have a problem that I am not sure whom > to address... Google did not reveal anything helpfull. > > I resently moved to kernel 2.6.0 (on Debian Sarge), and while everything > seems to work just fine, to my surprise gdb now fails to debug > executables that are linked against pthread: > > GNU gdb 5.3-debian > [snip] > This GDB was configured as "i386-linux"... > (gdb) b main > Breakpoint 1 at 0x80483a4: file foo.c, line 3. > (gdb) r > Starting program: /root/a.out > Error while reading shared library symbols: > Cannot find new threads: capability not available > Cannot find user-level thread for LWP 714: capability not available > > With kernel 2.4.22 this problem did not occur. Do you have any idea what > may have caused this problem, and how to solve it? If I can provide you > with any information that could be helpfull, please let me know. > > Kind regards, > > Maarten > > gcc version 3.3.2 (Debian) > GNU gdb 5.3-debian > GNU libc 2.3.2 > > >