From: ludo@gnu.org (Ludovic Courtès)
To: Doug Evans <xdje42@gmail.com>
Cc: guile-user@gnu.org,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Fun with LD_PRELOAD
Date: Tue, 04 Feb 2014 11:21:00 -0000 [thread overview]
Message-ID: <8761ovp1hw.fsf@gnu.org> (raw)
In-Reply-To: <CAP9bCMRsRrqEYG+7jS-m2EOhByAB+9hTFUuikoNJeJpxGATu5Q@mail.gmail.com> (Doug Evans's message of "Sun, 2 Feb 2014 14:08:18 -0800")
Hi, Doug,
Doug Evans <xdje42@gmail.com> skribis:
> It's kinda useful to see the system call tracing amongst gdb's own
> debug output, but my real goal is to explore ways of exercising gdb
> that are otherwise harder to do.
> With this I can script what happens when gdb does ptrace,waitpid,tkill,etc.
> Whether this exploration yields anything useful ... TBD.
Looks fun. So the main application would be to stress-test GDB and see
if it misses signals sent to application threads right when GDB is about
to stop them, for example, right?
Cheers,
Ludo’.
next prev parent reply other threads:[~2014-02-04 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 22:08 Doug Evans
2014-02-04 11:21 ` Ludovic Courtès [this message]
2014-02-05 18:21 ` Doug Evans
2014-02-05 19:11 ` Pedro Alves
2014-02-06 7:58 ` Doug Evans
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=8761ovp1hw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guile-user@gnu.org \
--cc=xdje42@gmail.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