Re: e_trapsignal removal

[christos%astron.com@localhost (Christos Zoulas)]

In article <19a85912-f444-6d2d-d09c-427843307ebb%gmx.com@localhost>,
Kamil Rytarowski  <n54%gmx.com@localhost> wrote:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>On 27.04.2018 21:11, Christos Zoulas wrote:
>> In article <b80b33fb-de4f-01dd-1705-716a2c0ecc73%gmx.com@localhost>,
>> Kamil Rytarowski  <n54%gmx.com@localhost> wrote:
>>> -=-=-=-=-=-
>>> -=-=-=-=-=-
>>>
>>> I propose to remove e_trapsignal from the compat framework
>>>
>>> Rationale:
>>> - It's currently unused. It was used for Darwin compat.
>>> - It's certainly broken and not used in part of the code where it could
>>> be used, generating a trap signal.
>>> - Maintaining debugging features in the compat framework is not a
>>> viable goal with the current resources.
>>>
>>> If we will ever want to run native Linux GDB or other debugger on the
>>> NetBSD kernel we will need to rework the existing code anyway.
>> 
>> I don't think this is for debuggers; it is there to remap the trap
>> and signal numbers on trap delivery to the traps and signals the
>> emulated application expects to receive:
>> 
>> https://nxr.netbsd.org/xref/src/sys/arch/x86/x86/linux_trap.c#145
>> 
>> christos
>> 
>
>My bad, I was thinking about e_tracesig!

Yes, that's unused...

christos