Da Zheng, le Tue 15 Dec 2009 23:16:11 +0800, a écrit :
> > That could be a glitch of some other mechanism. You can use disassemble
> > 0x01060089 to check what's really there and l * 0x01060089 to check
> > which precise file that comes from.
> disassemble is really useful:-) I really need to lear
Hi,
Thank you for your previous mail.
Samuel Thibault wrote:
> Hello again,
>
> Da Zheng, le Tue 15 Dec 2009 13:51:09 +0800, a écrit :
>> (gdb) run
>> Starting program: /root/hurd/ddekit_test/test
>> test1 thread starts at 1260701688
>> test1 thread wakes up at 1260701691
>> test1 thread enter
Hello again,
Da Zheng, le Tue 15 Dec 2009 13:51:09 +0800, a écrit :
> (gdb) run
> Starting program: /root/hurd/ddekit_test/test
> test1 thread starts at 1260701688
> test1 thread wakes up at 1260701691
> test1 thread enter a semaphore at 1260701691, timeout: 1
>
> Program received signal SIGSEGV
When you look in glibc, always look in the build tree as well, you'll
see evc_wait.S which is automatically built, calling the kernel_trap
macro.
Samuel
