This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC/PATCH] New convenience variable $_exitsignal
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>
- Cc: Tom Tromey <tromey at redhat dot com>, Pedro Alves <palves at redhat dot com>, Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>, "'GDB Patches'" <gdb-patches at sourceware dot org>
- Date: Tue, 17 Sep 2013 15:58:52 -0300
- Subject: Re: [RFC/PATCH] New convenience variable $_exitsignal
- Authentication-results: sourceware.org; auth=none
- References: <m3mwqqvagk dot fsf at redhat dot com> <00db01ce6b24$0b716aa0$22543fe0$ at muller@ics-cnrs.unistra.fr> <m3zjuotykn dot fsf at redhat dot com> <m37ghqn1as dot fsf at redhat dot com> <52374823 dot 4010203 at redhat dot com> <87bo3rxpko dot fsf at fleche dot redhat dot com> <1379444008 dot 2222 dot 35 dot camel at soleil>
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