https://bugs.kde.org/show_bug.cgi?id=452274
--- Comment #24 from Paul Floyd <pjfl...@wanadoo.fr> ---
(In reply to Nick Briggs from comment #22)
> I threw in a VG_(printf):
>
> @@ -3117,6 +3119,7 @@ VG_(fixup_guest_state_after_syscall_interrupted)(
> ThreadId tid,
> if (VG_(clo_trace_signals))
> VG_(message)( Vg_DebugMsg,
> " not in syscall at all: hmm, very suspicious\n" );
> + VG_(printf)("DEBUG: blksys_setup %ld ip %ld blksys_finished %ld\n",
> ML_(blksys_setup), ip, ML_(blksys_finished));
> /* Looks like we weren't in a syscall at all. Hmm. */
> vg_assert(sci->status.what != SsIdle);
> return;
>
> and see:
>
> DEBUG: vgPlain_client_syscall sysno 4
> DEBUG: vgPlain_client_syscall sysno 4
> DEBUG: vgPlain_client_syscall sysno 4
> DEBUG: vgPlain_client_syscall sysno 4
> DEBUG: blksys_setup 941235726 ip 941508929 blksys_finished 941235863
> DEBUG: vgPlain_client_syscall sci->status.what 2
> DEBUG: vgPlain_client_syscall sysno 1000
>
> and that ip is in x86g_calculate_eflags_all_WRK !
Very interesting.
--
You are receiving this mail because:
You are watching all bug changes.
