On 18/07/17 23:50 -0600, Jeff Law wrote:
On 07/07/2017 05:17 PM, John Marino wrote:
Right after DragonFly 4.8 was released (27 Mar 2017), the signal
trampoline was moved (twice) in response to a Ryzen bug. This broke
GCC's unwind support for DragonFly.
To avoid hardcoding the sigtramp
On 07/07/2017 05:17 PM, John Marino wrote:
> Right after DragonFly 4.8 was released (27 Mar 2017), the signal
> trampoline was moved (twice) in response to a Ryzen bug. This broke
> GCC's unwind support for DragonFly.
>
> To avoid hardcoding the sigtramp location to avoid issues like this in
>
Right after DragonFly 4.8 was released (27 Mar 2017), the signal
trampoline was moved (twice) in response to a Ryzen bug. This broke
GCC's unwind support for DragonFly.
To avoid hardcoding the sigtramp location to avoid issues like this in
the future, a new sysctl was added to DragonFly to
