https://bugs.kde.org/show_bug.cgi?id=452274
--- Comment #9 from Paul Floyd <pjfl...@wanadoo.fr> ---
Or more accurately, the guest seems to be performing (or just completed)
sigprocmask but the host is starting to make a new syscall.
The assert triggers because the host is expecting the syscall state to be idle
but it mist be something else (complete or hand to kernel, or a corrupt value).
Could you add something like
VG_(printf)("DEBUG: %s %d\n", __func__, sci->status.what);
just before the assert on line 2130 of m_syswrap/syswrap-main.c and report back
as to whether 'what' is 1, 2 or junk?
--
You are receiving this mail because:
You are watching all bug changes.
