|
From: Bob F. <bfr...@si...> - 2004-06-03 22:37:53
|
Released and CVS valgrind lack support for the relative new system calls timer_create, timer_settime, timer_gettime, timer_getoverrun, and timer_delete. These exist in Gentoo kernel 2.6.3. Quick question before I continue, is there a rule for the apparently random ordering of entries in the sys_info[] array? What order should functions be listed in? Starting with the latest CVS, I have added support for these calls. Unfortunately, I am seeing an assertion, and I don't think it is due to my updates. I ran valgrind on a relatively simple program which uses all the timer_* calls, and no problems were encountered. With a much more complex GUI program, I encounter this assertion: SYSCALL[22411,1]( 6):close ( 4 ) SYSCALL[22411,1]( 91):munmap ( 0x3C05B000, 4096 ) 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. ==22411== at 0xB80303C4: vgPlain_skin_assert_fail (vg_mylibc.c:1211) ==22411== by 0xB80303C3: assert_fail (vg_mylibc.c:1207) ==22411== by 0xB8030431: vgPlain_core_assert_fail (vg_mylibc.c:1218) ==22411== by 0xB8034B1A: vgPlain_handle_SCSS_change (vg_signals.c:447) ==22411== by 0xB8034EBF: vgPlain_do__NR_sigaction (vg_signals.c:588) ==22411== by 0xB804CF28: before_rt_sigaction (vg_syscalls.c:5175) ==22411== by 0xB804D3D9: vgPlain_pre_syscall (vg_syscalls.c:5594) ==22411== by 0xB800DFBE: sched_do_syscall (vg_scheduler.c:721) ==22411== by 0xB800E728: vgPlain_scheduler (vg_scheduler.c:1154) ==22411== by 0xB802AA09: main (vg_main.c:3038) sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==22411== at 0x3C000B12: (within /lib/ld-2.3.3.so) ==22411== by 0x3C8A3B09: sigaction (vg_libpthread.c:2066) ==22411== by 0x80B42AC: sigchld_handler_init() (qnx4helper.cc:158) ==22411== by 0x809F1AD: main (guiMain.cc:158 Any ideas? Bob ====================================== Bob Friesenhahn bfr...@si... http://www.simplesystems.org/users/bfriesen |