Sergey Bugaev, le mar. 16 avril 2024 10:10:11 +0300, a ecrit:
> On Tue, Apr 16, 2024 at 4:01 AM Samuel Thibault
> wrote:
> > Ah, no, I mis read the result. It does stay stuck on x86_64.
>
> Indeed, thanks. Reproduced and fixed; I was accidentally using rsp
> (instead of ursp) in one place.
Appl
On Tue, Apr 16, 2024 at 4:01 AM Samuel Thibault wrote:
> Ah, no, I mis read the result. It does stay stuck on x86_64.
Indeed, thanks. Reproduced and fixed; I was accidentally using rsp
(instead of ursp) in one place.
Sergey
-- >8 --
This tests generating and handling exceptions, thread_get_sta
Samuel Thibault, le mar. 16 avril 2024 02:59:39 +0200, a ecrit:
> Sergey Bugaev, le lun. 15 avril 2024 12:01:49 +0300, a ecrit:
> > This tests generating and handling exceptions, thread_get_state(),
> > thread_set_state(), and newly added thread_set_self_state(). It does
> > many of the same thing
Sergey Bugaev, le lun. 15 avril 2024 12:01:49 +0300, a ecrit:
> This tests generating and handling exceptions, thread_get_state(),
> thread_set_state(), and newly added thread_set_self_state(). It does
> many of the same things that glibc does when handling a signal.
> ---
> Note that I only teste
This tests generating and handling exceptions, thread_get_state(),
thread_set_state(), and newly added thread_set_self_state(). It does
many of the same things that glibc does when handling a signal.
---
Note that I only tested this on i386 and AArch64, not on x86_64.
tests/test-thread-state.c |
