Re: [Valgrind-developers] adding system call support

[Bob F. <bfr...@si...>]

On Thu, 3 Jun 2004, Tom Hughes wrote:

> In message <Pin...@sc...>
>          Bob Friesenhahn <bfr...@si...> wrote:
>
>> SYSCALL[22411,1](174) special:sigaction ( 17, 0x4FFFE684, 0x0 )
>>
>> valgrind: vg_signals.c:444 (vgPlain_handle_SCSS_change): Assertion `ksa_old.ksa_restorer == ((void *)0)' failed.
>
> That looks like the bug that Jeremy introduced this morning but it
> should be fixed now.

You are correct. Now that I am on the list, I will know about those 
commits.  I did another 'cvs update' and now the assertion is gone. 
There is a new error dump now:

==25335== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==25335==  Access not within mapped region at address 0x4A
==25335==    at 0x3C075AA9: (within /lib/librt-2.3.3.so)
==25335==    by 0x3C8A240D: pthread_once (vg_libpthread.c:1709)
==25335==    by 0x3C075228: timer_create (in /lib/librt-2.3.3.so)
==25335==    by 0x808A323: CTimeBox::CreateTimer() (TimeBox.cc:74)
==25335==    by 0x808B209: CTimeBox::CTimeBox(char*) (TimeBox.cc:126)
==25335==    by 0x809241B: InitializeFunct() (basefuncts.cc:548)
==25335==    by 0x809F2EE: main (guiMain.cc:218)
--25335-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
--25335-- si_code=1 Fault EIP: 0xB802FA3A; Faulting address: 0x2E322D73

valgrind: the `impossible' happened:
    Killed by fatal signal
Basic block ctr is approximately 77607320
==25335==    at 0xB803047C: vgPlain_core_panic (vg_mylibc.c:1230)
==25335==    by 0xB803047B: panic (vg_mylibc.c:1226)
==25335==    by 0xB803049C: vgPlain_core_panic (vg_mylibc.c:1231)
==25335==    by 0xB8037BB4: vg_sync_signalhandler (vg_signals.c:2225)
==25335==    by 0xB804D7E1: (within /usr/local/lib/valgrind/stage2)

======================================
Bob Friesenhahn
bfr...@si...
http://www.simplesystems.org/users/bfriesen