From: Tom Tromey <tromey@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFC/PATCH] Add new internal variable $_signo
Date: Wed, 17 Jul 2013 18:41:00 -0000 [thread overview]
Message-ID: <87bo61f2rv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3obb9y1aw.fsf@redhat.com> (Sergio Durigan Junior's message of "Thu, 13 Jun 2013 21:37:59 -0300")
>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
Sergio> Basically, the ABRT project (<https://fedorahosted.org/abrt/wiki>) wants
Sergio> to be able to perform some analysis on corefiles (to be implemented as a
Sergio> Python GDB module) and for that it needs to be able to inspect the
Sergio> signal which killed the program being investigated.
I read through this thread. It was very informative.
If you are not planning to tackle all the items Pedro pointed out, would
you mind filing bugs for the ones you are not planning to do?
Sergio> (gdb) core ./coredump
Sergio> [New LWP 2703]
Sergio> Core was generated by `/usr/bin/gnote <<skip>>'.
Sergio> Program terminated with signal 11, Segmentation fault.
Sergio> #0 0x09fa5348 in ?? ()
Sergio> (gdb) print $_siginfo.si_signo
Sergio> Unable to read siginfo
One other idea that occurs to me is that, in this situation, $_siginfo
could yield a value where only the si_signo bits are available. We've
already got all the machinery needed to make this work.
TBH I'm not sure if this idea is clever and simple, or obscure and hard
to use.
The one major benefit, I think, would be that scripts could simply use
$_siginfo.si_signo unconditionally.
Tom
prev parent reply other threads:[~2013-07-17 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 2:39 Sergio Durigan Junior
2013-06-14 7:49 ` Eli Zaretskii
2013-06-16 6:08 ` Sergio Durigan Junior
2013-06-14 8:59 ` Mark Kettenis
2013-06-14 9:37 ` Pierre Muller
2013-06-14 17:59 ` Sergio Durigan Junior
2013-06-14 20:36 ` Pedro Alves
2013-06-15 6:46 ` Sergio Durigan Junior
2013-06-17 17:02 ` Pedro Alves
2013-06-14 17:58 ` Pedro Alves
2013-06-16 5:57 ` Sergio Durigan Junior
2013-06-16 6:25 ` Sergio Durigan Junior
2013-06-17 17:20 ` Pedro Alves
2013-07-17 18:41 ` Tom Tromey [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=87bo61f2rv.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@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