This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Create avr-linux-tdep.c (add reintroduce gdbarch_gdb_signal_{to,from}_target for that target)
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Joern Rennecke <joern dot rennecke at embecosm dot com>
- Cc: GDB Patches <gdb-patches at sourceware dot org>, Pedro Alves <palves at redhat dot com>
- Date: Mon, 12 Aug 2013 18:48:57 -0300
- Subject: Re: [PATCH] Create avr-linux-tdep.c (add reintroduce gdbarch_gdb_signal_{to,from}_target for that target)
- References: <m3wqnqvgh8 dot fsf at redhat dot com> <20130812171901 dot 7mi3vkyoro40kwcc-nzlynne at webmail dot spamcop dot net>
On Monday, August 12 2013, Joern Rennecke wrote:
> Quoting Sergio Durigan Junior <sergiodj@redhat.com>:
>
>
>> +avr-*-*linux*)
>> + # Target: AVR Linux
>> + gdb_target_obs="avr-tdep.o avr-linux-tdep.o linux-tdep.o"
>> + gdb_sim=../sim/avr/libsim.a
>> + ;;
>> +
>> avr-*-*)
>> # Target: AVR
>> gdb_target_obs="avr-tdep.o"
>>
>
> That is creating a new target.
Yes.
> So are users using a linux host supposed
> to configure for this new target? But why does it look like it's the
> target that is running linux - there is no such thing for avr.
> Shouldn't we rather autoconf the host signals?
These are not host signals, they are the target's.
Maybe I am confusing things here. I saw
<arch/avr32/include/uapi/asm/signal.h> and I assumed one could run Linux
on AVR, but on a further investigation I saw that it only applies to
AVR32, right? I'm definitely not an expert here, sorry about it.
But well, if that is the case, then I guess we can either (a) treat
AVR32 separately and make an avr32-linux-tdep.c for it, or (b) drop this
patch entirely.
WDYT? Am I missing something here?
--
Sergio