This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 00/17] Implement gdbarch_gdb_signal_to_target
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: GDB Patches <gdb-patches at sourceware dot org>
- Date: Mon, 01 Jul 2013 07:40:35 -0300
- Subject: Re: [PATCH 00/17] Implement gdbarch_gdb_signal_to_target
- References: <1372664545-3947-1-git-send-email-sergiodj at redhat dot com> <mvm1u7ifz6g dot fsf at hawking dot suse dot de>
On Monday, July 01 2013, Andreas Schwab wrote:
> Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
>> What I did was to investigate, on the Linux kernel, which targets shared
>> the signal numbers definition with x86. My approach was to make the x86
>> the "de facto" implementation, and extend only the needed bits on each
>> arch. For the record, I used linux-3.10-rc6 as the main source of
>> information, always looking at
>> arch/<ARCH_NAME>/include/uapi/asm/signal.h. For SIGRTMAX (which defaults
>> to _NSIG in most cases), I had to look at different signal-related
>> files, but most of them (except MIPS) were defined to 64 anyway.
>
> There is also include/uapi/asm-generic/signal.h (which happens to agree
> with x86 numbering) which will be used for every new architecture port.
Thanks for pointing that out.
> (Looks like you missed out aarch64.)
Indeed. I will submit the patch with the funny subject "[PATCH
18/17]".
Thanks,
--
Sergio