From: jose.marchesi@oracle.com (Jose E. Marchesi)
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Support for the $_siginfo convenience var in sparc64
Date: Tue, 03 Dec 2013 11:59:00 -0000 [thread overview]
Message-ID: <87d2lew3fb.fsf@oracle.com> (raw)
In-Reply-To: <87zjq1s9ww.fsf@oracle.com> (Jose E. Marchesi's message of "Tue, 22 Oct 2013 15:38:23 +0200")
ping
> The following patch adds support for the $_siginfo convenience variable
> to sparc64-*-linux-gnu targets.
I take it from the patch that linux-tdep.c:linux_get_siginfo_type wouldn't
work for sparc64? Why is that? What's different?
These are the differences of glibc's bits/siginfo.h in sparc with
respect to bits/siginfo.h in x86:
- The _sigfault struct has an additional field `int si_trapno'.
- The `si_band' field in the `_sigpoll' struct is of type `int' instead
of `long int'.
It would be nice to avoid all that code repetition, but since glibc
maintains per-target bits/signinfo.h files more differences could be
introduced in the future...
next prev parent reply other threads:[~2013-12-03 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 13:09 Jose E. Marchesi
2013-10-22 13:21 ` Pedro Alves
2013-10-22 13:36 ` Jose E. Marchesi
2013-12-03 11:59 ` Jose E. Marchesi [this message]
2013-12-03 17:06 ` Pedro Alves
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=87d2lew3fb.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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