From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [RFC 5/5] uprobes: add global breakpoints
Date: Thu, 09 Aug 2012 18:25:00 -0000 [thread overview]
Message-ID: <5024008F.9070206@earthlink.net> (raw)
In-Reply-To: <1344355952-2382-6-git-send-email-bigeasy@linutronix.de>
On 8/7/12 9:12 AM, Sebastian Andrzej Siewior wrote:
> What I miss right now is an interface to tell the user/gdb that there is a
> program that hit a global breakpoint and is waiting for further instructions.
> A "tail -f trace" does not work and may contain also a lot of other
> informations. I've been thinking about a poll()able file which returns pids of
> tasks which are put on hold. Other suggestions?
>
In case anybody is having a mysterious sense of deja vu about this, my
patch last year for global breakpoints (
http://sourceware.org/ml/gdb-patches/2011-06/msg00163.html and friends)
had the same issue, and solved this by opening a device /dev/breakpoint
and hooking it up to a GDB event handler. (GDB event handling
ultimately calls poll() on the collection of event sources.)
Stan
stan@codesourcery.com
next prev parent reply other threads:[~2012-08-09 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1344355952-2382-1-git-send-email-bigeasy@linutronix.de>
2012-08-07 16:13 ` Sebastian Andrzej Siewior
2012-08-08 13:19 ` Oleg Nesterov
2012-08-09 17:18 ` Sebastian Andrzej Siewior
2012-08-13 13:20 ` Oleg Nesterov
2012-08-14 11:44 ` Sebastian Andrzej Siewior
2012-08-09 18:25 ` Stan Shebs [this message]
2012-08-13 11:35 ` Peter Zijlstra
2012-08-20 15:27 ` Sebastian Andrzej Siewior
2012-08-21 19:42 ` [RFC 5/5 v2] " Sebastian Andrzej Siewior
2012-08-22 13:53 ` Oleg Nesterov
2012-08-27 18:57 ` Sebastian Andrzej Siewior
2012-08-29 15:48 ` Oleg Nesterov
2012-08-30 20:42 ` Sebastian Andrzej Siewior
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=5024008F.9070206@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb-patches@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