|
From: Jeremy F. <je...@go...> - 2005-03-12 00:40:20
|
Tom Truscott wrote:
>valgrind-2.4.0.rc2 is quite nice but it (and rc1) sometimes glitches
>if I resize the window after it starts running:
>
> valgrind: vg_syscalls.c:6106 (vgPlain_client_syscall): Assertion `tst->sig_mask.sig[0] == tst->tmp_sig_mask.sig[0]' failed.
> ==9054== at 0xB002E2C9: ??? (vg_mylibc.c:1166)
> ==9054== by 0xB002E2C8: assert_fail (vg_mylibc.c:1166)
> ==9054== by 0xB002E307: vgPlain_core_assert_fail (vg_mylibc.c:1177)
> ==9054== by 0xB004C4AD: vgPlain_client_syscall (vg_syscalls.c:6194)
> ==9054== by 0xB00159B0: handle_syscall (vg_scheduler.c:632)
> ==9054== by 0xB0015C5A: vgPlain_scheduler (vg_scheduler.c:733)
> ==9054== by 0xB006EB3A: vgArch_thread_wrapper (core_os.c:69)
>[...]
>As a possible clue, I noticed that if one runs the following program
>and then changes the window size, it remains pause()d when run standalone
>but terminates when run under valgrind.
>
>
I've fixed the unexpected interrupted syscall problem, but the assertion
failure is still a concern; it shouldn't have happened either way. Can
you reproduce it with CVS HEAD?
J
|