From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: Tom Tromey <tromey@redhat.com>, Pedro Alves <palves@redhat.com>,
Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
"'GDB Patches'" <gdb-patches@sourceware.org>
Subject: Re: [RFC/PATCH] New convenience variable $_exitsignal
Date: Tue, 17 Sep 2013 18:59:00 -0000 [thread overview]
Message-ID: <m3bo3rnukz.fsf@redhat.com> (raw)
In-Reply-To: <1379444008.2222.35.camel@soleil> (Philippe Waroquiers's message of "Tue, 17 Sep 2013 20:53:28 +0200")
On Tuesday, September 17 2013, Philippe Waroquiers wrote:
> On Tue, 2013-09-17 at 12:36 -0600, Tom Tromey wrote:
>
>> Another consideration along these lines is that I have a branch in
>> progress for "catch exit" -- it's been waiting for Sergio's work on
>> these convenience variables. I think here as well $_exitsignal seems
>> like a natural fit, even though the process has not technically exited
>> at the catchpoint.
> Will there be (significant) functional differences between
> "catch exit"
> and
> "catch syscall exit exit_group" ?
I think this is more like "catch fork" and "catch syscall fork clone".
ptrace already offers PTRACE_O_TRACEEXIT so we could be using that even
when "catch syscall" is not fully functional on the target (i.e.,
there's no XML file to translate syscalls names to numbers). But Tom
may correct me here.
--
Sergio
next prev parent reply other threads:[~2013-09-17 18:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 6:30 Sergio Durigan Junior
2013-06-16 16:22 ` Doug Evans
2013-06-17 3:33 ` Eli Zaretskii
2013-06-17 7:32 ` Pierre Muller
2013-06-17 17:55 ` Sergio Durigan Junior
2013-06-19 5:26 ` Sergio Durigan Junior
2013-09-16 18:04 ` Pedro Alves
2013-09-17 0:11 ` Sergio Durigan Junior
2013-09-17 16:19 ` Pedro Alves
2013-09-17 18:39 ` Tom Tromey
2013-09-17 18:53 ` Philippe Waroquiers
2013-09-17 18:59 ` Sergio Durigan Junior [this message]
2013-09-17 18:59 ` Tom Tromey
2013-09-17 19:08 ` Pedro Alves
2013-09-17 19:02 ` Pedro Alves
2013-09-17 19:09 ` Tom Tromey
2013-07-18 16:48 ` Tom Tromey
2013-06-17 17:28 ` Pedro Alves
2013-06-17 17:31 ` Pedro Alves
2013-06-17 17:41 ` Sergio Durigan Junior
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=m3bo3rnukz.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=philippe.waroquiers@skynet.be \
--cc=pierre.muller@ics-cnrs.unistra.fr \
--cc=tromey@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