On 1/13/24 07:57, Robbin Ehn wrote:
Commit f4e1168198 (linux-user: Split out host_sig{segv,bus}_handler)
introduced a bug, when returning from host_sigbus_handler the PC is
never set. Thus cpu_loop_exit_restore is called with a zero PC and
we immediate get a SIGSEGV.
Signed-off-by: Robbin Ehn
-
Hi, Palmer,
On Fri, Jan 12, 2024 at 10:03 PM Palmer Dabbelt wrote:
>
> On Fri, 12 Jan 2024 12:57:22 PST (-0800), r...@rivosinc.com wrote:
> > Commit f4e1168198 (linux-user: Split out host_sig{segv,bus}_handler)
> > introduced a bug, when returning from host_sigbus_handler the PC is
>
> So we shou
On Fri, 12 Jan 2024 12:57:22 PST (-0800), r...@rivosinc.com wrote:
Commit f4e1168198 (linux-user: Split out host_sig{segv,bus}_handler)
introduced a bug, when returning from host_sigbus_handler the PC is
So we should probably have a
Fixes: f4e1168198 ("linux-user: Split out host_sig{segv,bus}_
Commit f4e1168198 (linux-user: Split out host_sig{segv,bus}_handler)
introduced a bug, when returning from host_sigbus_handler the PC is
never set. Thus cpu_loop_exit_restore is called with a zero PC and
we immediate get a SIGSEGV.
Signed-off-by: Robbin Ehn
---
linux-user/signal.c | 5 +++--
1 f