From: Daniel Jacobowitz <drow@mvista.com>
To: Denis J Barrow <DJ@de.ibm.com>
Cc: gdb@sources.redhat.com, Jeff Dike <jdike@karaya.com>
Subject: Re: question wrt clone & gdb
Date: Mon, 03 Feb 2003 13:44:00 -0000 [thread overview]
Message-ID: <20030203134423.GA3383@nevyn.them.org> (raw)
In-Reply-To: <OF6F6DDCAB.FCA474EA-ONC1256CC2.0044C9A0-C1256CC2.0044D76C@de.ibm.com>
On Mon, Feb 03, 2003 at 01:33:07PM +0100, Denis J Barrow wrote:
> Hi
> Is it correct to say that gdb doesnt support use of the raw clone call for
> multi threaded apps under linux with gdb &
> one must use pthreads for linux if one intends to use gdb for debugging
> purposes ?, I am personally about 80% sure that this is the case
> & have heard from a reliable source that this is still the case.
Yes. There are limited plans to change this, but no one's had
time/motivation to do it.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-03 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 12:33 Denis J Barrow
2003-02-03 13:44 ` Daniel Jacobowitz [this message]
2003-02-03 15:47 Denis J Barrow
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=20030203134423.GA3383@nevyn.them.org \
--to=drow@mvista.com \
--cc=DJ@de.ibm.com \
--cc=gdb@sources.redhat.com \
--cc=jdike@karaya.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