From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14830 invoked by alias); 12 Jan 2009 19:29:25 -0000 Received: (qmail 14822 invoked by uid 22791); 12 Jan 2009 19:29:24 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 12 Jan 2009 19:28:43 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id CF5A510598; Mon, 12 Jan 2009 19:28:41 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id B4E8C10497; Mon, 12 Jan 2009 19:28:41 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1LMSSn-0001Ab-Ai; Mon, 12 Jan 2009 14:28:41 -0500 Date: Mon, 12 Jan 2009 19:29:00 -0000 From: Daniel Jacobowitz To: Mathieu Lacage Cc: gdb@sourceware.org Subject: Re: weird errors when notifying gdb of linkmap changes Message-ID: <20090112192841.GA4460@caradoc.them.org> Mail-Followup-To: Mathieu Lacage , gdb@sourceware.org References: <74fef6df0901121120m52fa4dacrb797a9b750da3d43@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <74fef6df0901121120m52fa4dacrb797a9b750da3d43@mail.gmail.com> User-Agent: Mutt/1.5.17 (2008-05-11) 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/msg00059.txt.bz2 On Mon, Jan 12, 2009 at 08:20:01PM +0100, Mathieu Lacage wrote: > hi, > > I get the following errors: > Starting program: /home/mathieu/code/elf-loader/ls > [Thread debugging using libthread_db enabled] > Error while reading shared library symbols: > Cannot find new threads: generic error > Cannot find new threads: generic error > (gdb) bt > #0 0xb7f228d1 in _r_debug_state () at gdb.c:10 > #1 0xb7f22964 in gdb_notify () at gdb.c:36 > #2 0xb7f1d7fd in stage2 (args= > {interpreter_load_base = 3086077952, program_phdr = 0x8048034, > program_phnum = 8, sysinfo = 3086074880, program_argc = 1, > program_argv = 0xbfa13ff4, program_envp = 0xbfa13ffc}) at ldso.c:253 > #3 0xb7f1d9b0 in stage1 () at ldso.c:312 > #4 0x00000001 in ?? () > > I wonder if there is an obvious well-known reason for this. You'll have to build a debuggable libthread_db to figure out what it's complaining about. Most likely you have told it that the thread library is loaded, but provided some incorrect information that led to GDB not finding the thread library's data structures. -- Daniel Jacobowitz CodeSourcery