From: Keith Seitz <keiths@redhat.com>
To: Bruce Korb <bkorb@pacbell.net>
Cc: insight@sources.redhat.com
Subject: Re: multi-threaded debugging using Insight
Date: Thu, 03 Oct 2002 09:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0210030903220.1509-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <3D9C6844.21E6778@pacbell.net>
On Thu, 3 Oct 2002, Bruce Korb wrote:
> I'm still interested to know if it is supposed to be possible.
> My use of popen seems to cause a problem, but there is no FAQ
> and the folks on the gdb list did not even reply. I solved my
> immediate problem using printf debugging, but I would prefer
> to use an interactive debugger. Much easier. Is multi-process
> debugging new territory?
What's the problem again? Yes, Insight/gdb should be able to debug a
multi-threaded application. Can you follow forks and stuff into the forked
child? No, that was never implemented (in GDB) for anything but HP.
Keith
next prev parent reply other threads:[~2002-10-03 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 22:22 Remote debug " Masahide Tomita
2002-10-03 8:40 ` Keith Seitz
2002-10-03 8:54 ` multi-threaded debugging " Bruce Korb
2002-10-03 9:01 ` Keith Seitz [this message]
2002-10-03 10:28 ` Bruce Korb
2002-10-03 10:35 ` Keith Seitz
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=Pine.LNX.4.44.0210030903220.1509-100000@valrhona.uglyboxes.com \
--to=keiths@redhat.com \
--cc=bkorb@pacbell.net \
--cc=insight@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).