From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org,
Binutils Development <binutils@sourceware.org>
Subject: Re: RFC: handle new NT_SIGINFO note in gdb
Date: Tue, 30 Oct 2012 18:31:00 -0000 [thread overview]
Message-ID: <50901CE2.2070407@redhat.com> (raw)
In-Reply-To: <878vanyj3k.fsf@fleche.redhat.com>
On 10/30/2012 05:18 PM, Tom Tromey wrote:
> This patch adds support for the new Linux NT_SIGINFO core note to gdb.
>
> First, I've CCd the binutils list because this includes a BFD change.
> In particular, in order to access the note data, I changed BFD to make a
> pseudosection for this new note's data. This seemed ok based on
> surrounding code; but if some other method is preferred, just let me
> know and I will implement that instead.
>
> On the gdb side the support is relatively straightforward.
>
All looks great to me. Thanks Tom.
> I chose to implement the support directly in corelow, since adding a new
> hook just for this functionality seemed like overkill.
>
> A new test case is included. It uses "gcore" and then re-reads the
> siginfo data from the generated core.
>
> Built and regtested on x86-64 Fedora 16.
> On the binutils side, I remembered this time to run the test suite in
> binutils, gas, and ld.
--
Pedro Alves
next prev parent reply other threads:[~2012-10-30 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 17:18 Tom Tromey
2012-10-30 18:31 ` Pedro Alves [this message]
2012-11-01 1:12 ` Alan Modra
[not found] <878vanyj3k.fsf__16012.8015945249$1351617533$gmane$org@fleche.redhat.com>
2012-11-01 19:01 ` Tom Tromey
2012-11-02 18:21 ` Tom Tromey
2012-11-02 19:02 ` Pedro Alves
2012-11-02 19:32 ` Tom Tromey
2012-11-05 18:11 ` Pedro Alves
2012-11-08 21:10 ` Tom Tromey
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=50901CE2.2070407@redhat.com \
--to=palves@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--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