Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: zoka <zoran@microtrol.com.au>
Cc: gdb@sourceware.org
Subject: Re: Incorrect GDB backtrace for pthreads
Date: Thu, 13 Sep 2007 16:49:00 -0000	[thread overview]
Message-ID: <20070913145854.GA27458@caradoc.them.org> (raw)
In-Reply-To: <12654909.post@talk.nabble.com>

On Thu, Sep 13, 2007 at 07:39:05AM -0700, zoka wrote:
> Starting program: /home/zoka/gdb/threads
> Failed to read a valid object file image from memory.

> #0  0xffffe410 in ?? ()                          # backtrace incorrect

This is a kernel bug.

> (gdb) info threads                                # GDB knows no threads ?!

It sounds like either shared library debugging doesn't work on your
system, or thread debugging doesn't.  ld.so and libpthread.so are
probably stripped.  They need a symbol table for GDB to work.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-09-13 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 14:56 zoka
2007-09-13 16:49 ` Daniel Jacobowitz [this message]

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=20070913145854.GA27458@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=zoran@microtrol.com.au \
    /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