Re: Etch pthread_mutex_lock - bad backtrace
On Thu, 13 Nov 2008 11:48:54 +0100
Tudor Golubenco <tudor@golubenco.org> wrote:
> Also, I would appreciate if you could run the
> above program on your Etch system and let me know if you can get a
> meaningful bt.
This is on testing:
lee@cat:~$ gcc test.c -o testprog
/tmp/ccs4xx0w.o: In function `main':
test.c:(.text+0x4f): undefined reference to `pthread_create'
test.c:(.text+0x73): undefined reference to `pthread_create'
collect2: ld returned 1 exit status
lee@cat:~$ gcc test.c -o testprog -lpthread
lee@cat:~$ ./testprog
(gdb) attach 25853
Attaching to process 25853
Reading symbols from /home/lee/testprog...done.
Reading symbols from /lib/i686/cmov/libpthread.so.0...done.
[Thread debugging using libthread_db enabled]
[New Thread 0xb7e45ad0 (LWP 25853)]
[New Thread 0xb7643b90 (LWP 25855)]
[New Thread 0xb7e44b90 (LWP 25854)]
Loaded symbols for /lib/i686/cmov/libpthread.so.0
Reading symbols from /lib/i686/cmov/libc.so.6...done.
Loaded symbols for /lib/i686/cmov/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
0xb7fd7424 in __kernel_vsyscall ()
(gdb) backtrace
#0 0xb7fd7424 in __kernel_vsyscall ()
#1 0xb7faea71 in pause () from /lib/i686/cmov/libpthread.so.0
#2 0x08048510 in main ()
(gdb)
Is that meaningful?
Reply to: