From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <Michael.Snyder@palmsource.com>
Cc: GDB General ML <gdb@sourceware.org>,
Ewa Matejska <Ewa.Matejska@palmsource.com>
Subject: Re: Follow-fork with gdbserver
Date: Wed, 23 Aug 2006 03:43:00 -0000 [thread overview]
Message-ID: <20060823034351.GA9228@nevyn.them.org> (raw)
In-Reply-To: <1156293099.9019.28.camel@localhost.localdomain>
On Tue, Aug 22, 2006 at 05:31:39PM -0700, Michael Snyder wrote:
> Hey Daniel,
>
> How difficult, and how interesting, do you think it would be
> to add follow-fork support to gdbserver for native linux?
I did it once for a customer. It wasn't terribly hard, but it was an
incredibly bad hack, because GDB normally does some futzing around with
breakpoints on fork events; gdbserver doesn't have a breakpoint list,
so it doesn't know what to do. So I had it capture some memory writes
and replay them.
Nowadays gdbserver still doesn't set software breakpoints (Z0/z0), but
it does have most of the infrastructure to do it. So, it would
probably be easier to design the new packets without my ugly hack.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-08-23 3:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 0:31 Michael Snyder
2006-08-23 3:43 ` 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=20060823034351.GA9228@nevyn.them.org \
--to=drow@false.org \
--cc=Ewa.Matejska@palmsource.com \
--cc=Michael.Snyder@palmsource.com \
--cc=gdb@sourceware.org \
/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