On Mon, 19 Apr 2021 at 21:36, Richard Henderson <richard.hender...@linaro.org> wrote: > > Using cpu_abort takes care of things like unregistering a > SIGABRT handler for user-only.
I would find this argument more persuasive if we didn't have a ton of other places where we call abort() or assert() or g_assert_not_reached(). Either we should have a consistent mechanism for assertions in linux-user turning off the SIGABRT handler, or we should just not worry about it on the basis that it's a "can't happen" error anyway... thanks -- PMM