From: fche@redhat.com (Frank Ch. Eigler)
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: [RFC] Global breakpoints
Date: Wed, 05 May 2010 00:17:00 -0000 [thread overview]
Message-ID: <y0my6fzjj72.fsf@fche.csb> (raw)
In-Reply-To: <4BE0A112.8080503@codesourcery.com> (Stan Shebs's message of "Tue, 04 May 2010 15:34:58 -0700")
Stan Shebs <stan@codesourcery.com> writes:
> [...] Implementation in Linux is going to be kind of freaky. It's
> not desirable to have GDB attach to every process in sight
> preemptively, nor to have GDBserver do it, which means that we're
> talking about something like a mini GDB stub embedded in a kernel
> module. [...]
You could check out our gdbstub-in-kernel prototype. It has the
benefit that it is not a 'mini' stub but in time a full gdbserver
substitute. It has the unbenefit that it is built on utrace, which is
a source of controversy. OTOH, gdb embracing it could just blow out
the flames, which would be oh so nice.
http://lkml.org/lkml/2009/11/30/173
git://elastic.org/~fche/utrace-ext.git branch utrace-gdbstub-uprobes
- FChE
prev parent reply other threads:[~2010-05-05 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 22:35 Stan Shebs
2010-05-04 23:34 ` David Daney
2010-05-05 0:17 ` Frank Ch. Eigler [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=y0my6fzjj72.fsf@fche.csb \
--to=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=stan@codesourcery.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