From: Daniel Jacobowitz <drow@false.org>
To: lapo.pasqui@tele2.it
Cc: gdb@sources.redhat.com
Subject: Re: Is NPTL needed for debugging multi-thread application
Date: Thu, 27 May 2004 12:59:00 -0000 [thread overview]
Message-ID: <20040527125924.GA32439@nevyn.them.org> (raw)
In-Reply-To: <auto-000044773074@mailfe01.swip.net>
On Thu, May 27, 2004 at 10:30:12AM +0200, lapo.pasqui@tele2.it wrote:
> Hi
> I'm having problem in debugging multi thread application on a PPC board. As soon as it hit a breakpoint on a secondary thread I get a SIGKILL from the gdb.
> Looking at the core file generated by gdb itself, it looks like it is having problem in navigating the stack of a thread.
>
> I'm using glibc w/o the NTPL implementation (I'm using the linux thread library).
>
> Could it explain the problem? Does it only work with NPTL threads?
No, LinuxThreads has worked for a long time. This isn't enough
information to figure out what's wrong.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-05-27 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 8:30 lapo.pasqui
2004-05-27 12:59 ` 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=20040527125924.GA32439@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=lapo.pasqui@tele2.it \
/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