Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Steven J. Hill" <sjhill@realitydiluted.com>
Cc: gdb@sourceware.org
Subject: Re: Linux threads and insight 6.4 / 6.5
Date: Fri, 30 Jun 2006 17:27:00 -0000	[thread overview]
Message-ID: <20060628140217.GA12463@nevyn.them.org> (raw)
In-Reply-To: <44A1D5D2.9050705@realitydiluted.com>

On Tue, Jun 27, 2006 at 08:05:22PM -0500, Steven J. Hill wrote:
> Daniel Jacobowitz wrote:
> > 
> > With signal 5 is a clear signal that gdbserver has not enabled thread
> > support, either because of a mismatch or a problem with libthread_db
> > support on your target.  When one thread hits a breakpoint, if another
> > thread is running outside of debugger control, the kernel may terminate
> > the entire process.
> > 
> Using glibc NPTL with both gdb and gdbserver compiled from the same 6.4
> source and gdbserver built against the exact same NPTL libraries I get:
> 
>    Cannot find new threads: capability not available
> 
> with an eventual termination of the process. So what mismatch or problem
> with libthread_db should I be looking for? Thanks.

Try HEAD.  You didn't say what platform you were using, but guessing
MIPS, you need something newer.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-06-28 14:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28  7:10 FALE(Leopold Faschalek)
2006-06-29 11:53 ` Steven J. Hill
2006-06-29 15:14   ` Daniel Jacobowitz
2006-06-30  0:11     ` Steven J. Hill
2006-06-30 17:27       ` 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=20060628140217.GA12463@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=sjhill@realitydiluted.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