Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mathieu Lacage <mathieu.lacage@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: weird errors when notifying gdb of linkmap changes
Date: Mon, 12 Jan 2009 19:29:00 -0000	[thread overview]
Message-ID: <20090112192841.GA4460@caradoc.them.org> (raw)
In-Reply-To: <74fef6df0901121120m52fa4dacrb797a9b750da3d43@mail.gmail.com>

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


  reply	other threads:[~2009-01-12 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 19:20 Mathieu Lacage
2009-01-12 19:29 ` Daniel Jacobowitz [this message]
2009-01-13  9:45   ` Mathieu Lacage

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090112192841.GA4460@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=mathieu.lacage@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox