Re: MIPS Linux signals

[Aleksandar Ristovski <aristovski at qnx dot com>]

On 12-05-22 06:57 AM, Pedro Alves wrote:
> [Adding Aleksandar]
>
> Answering this one.
>
> On 05/21/2012 11:48 PM, Maciej W. Rozycki wrote:
>
> >   Shall we drop the unused gdbarch API so as to avoid further confusion
> > then?
>
>
> If we don't find a use for it, yes.
>
> Aleksandar, we're discussing gdbarch_target_signal_from_host and
> gdbarch_target_signal_to_host.  It turns out that uses to either of those
> were never added to GDB.  gdbarch_target_signal_FROM_host's purpose is clear,
> and we're about to add a (new) use to fix the same situation you ran into at the
> time (cross core debugging).  I'm wondering if you ever found a use for
> gdbarch_target_signal_TO_host that we should consider, though.

The API was added to introduce consistency between gdb's view of 
target's numeric signal values and actual numerical signal values of the 
target. In general case, they should *not* be viewed as the same, but 
rather as distinct numeric sets which happen to have common names. When 
cross-examining a core this becomes very obvious, but it is also very 
obvious when debugging remote target which has different numerical 
values for signals.

I use both from_host and to_host.


That being said, I'm not sure why I never submitted actual uses for nto 
target... I have it in our repository.


Looking at the code now, I see why. I use it in our remote target (we 
have our own) and thus perform translation on-the-fly. Gdb receives 
correct GDB version as well as target (when gdb sends it).



Thanks,

Aleksandar