This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 05/17] ARM support
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: GDB Patches <gdb-patches at sourceware dot org>
- Date: Thu, 25 Jul 2013 03:25:35 -0300
- Subject: Re: [PATCH 05/17] ARM support
- References: <1372664545-3947-1-git-send-email-sergiodj at redhat dot com> <1372664545-3947-6-git-send-email-sergiodj at redhat dot com> <877ggpgl1u dot fsf at fleche dot redhat dot com>
On Wednesday, July 17 2013, Tom Tromey wrote:
>>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio> Support for the ARM target. Even though ARM shares almost everything
> Sergio> with x86 regarding signal numbers, there is SIGSWI which is an ARM-only
> Sergio> signal as far as I have verified. However, GDB's internal signal
> Sergio> definition does not recognize SIGSWI, so there is nothing we can/must
> Sergio> do.
>
> I think this is a bit peculiar in a couple of ways.
>
> SIGSWI has the same value as SIGRTMIN.
> So there is some confusion somewhere.
> At the very least, it seems like if this is correct, then we maybe
> couldn't sensible translate SIGSWI.
No, apparently we couldn't. Doing a further investigation on the kernel
sources, the only mention I found to SIGSWI (not counting the
declaration itself) is on the file <arch/arm/kernel/arthur.c>, some
apparently odd ARM-based (RISCOS) OS which uses this communicate with
its emulator somehow. It is called Arthur OS, and I don't think we
support it in any way.
So, after seeing this, I think we shouldn't care about this until we
choose to support the OS.
> Second, the new enum seems like dead code. It's only a matter of time
> until someone notices and removes it. Perhaps a comment somewhere would
> be better.
Fair enough, I will make a comment somewhere explaining this.
Thanks,
--
Sergio