|
From: Tom H. <th...@cy...> - 2003-11-06 11:54:12
|
In message <yek...@au...>
Tom Hughes <th...@cy...> wrote:
> There appears to be a bug in the new system call handling that causes
> a system call to get executed twice sometimes, seemingly when a signal
> occurs at the wrong time.
One other thing that I forgot to mention is that the test program will
also sometimes cause valgrind to assert as follows:
valgrind: vg_proxylwp.c:1144 (sys_wait_results): Assertion `res.syscallno == tst->syscallno' failed.
==8959== at 0x4016E8AA: vgPlain_skin_assert_fail (vg_mylibc.c:1103)
==8959== by 0x4016E8A9: assert_fail (vg_mylibc.c:1099)
==8959== by 0x4016E904: vgPlain_core_assert_fail (vg_mylibc.c:1110)
==8959== by 0x40172148: sys_wait_results (vg_proxylwp.c:1155)
sched status:
Thread 1: status = WaitSys, associated_mx = 0x0, associated_cv = 0x0
==8959== at 0x804855C: alarm_handler (in /home/thh/vgtest/sigtest)
==8959== by 0x40248A06: __libc_start_main (in /lib/i686/libc-2.3.2.so)
==8959== by 0x80484CC: ??? (start.S:81)
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|