|
From: Bob F. <bfr...@si...> - 2004-06-12 16:58:55
|
On Sat, 12 Jun 2004, Tom Hughes wrote: >> Unfortunately I did not record the exact assertion message and don't >> have an unmodified valgrind immediately available. However, the >> assertion was from valgrind and was due to support for timer_create >> not being implemented. It said not to "panic" since it is easy to add >> system calls to valgrind. > > Was it this message? > > --9067-- WARNING: unhandled syscall: 266 > --9067-- Do not panic. You may be able to fix this easily. > --9067-- Read the file README_MISSING_SYSCALL_OR_IOCTL. > > If so then that isn't an assertion, it's just a warning and valgrind > will happily carry on return ENOSYS to the application code. Yes, it was this message. I must have been confused. However, the program did immediately crash after this point. It was probably our own assertion because timer_create returned an error. Clearly more investigation on my part is necessary. Bob ====================================== Bob Friesenhahn bfr...@si... http://www.simplesystems.org/users/bfriesen |