bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

linuxthreads problem?


From: Justin
Subject: linuxthreads problem?
Date: Fri, 23 Feb 2001 20:46:09 -0800 (PST)

Starting program: /usr/local/tcl/bin/tclsh8.4
[New Thread 1024 (LWP 10166)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 10166)]
__pthread_alt_lock (lock=0x40201cfc, self=0x0) at spinlock.c:406
406       do {
(gdb) bt
#0  __pthread_alt_lock (lock=0x40201cfc, self=0x0) at spinlock.c:406
#1  0x400b37a6 in __pthread_mutex_lock (mutex=0x40201cec) at mutex.c:120
#2  0x401ea2f1 in __register_frame_info (begin=0x40201df8, ob=0x402038e0)
    at ../../gcc/gcc/frame-dwarf2.c:561
#3  0x400fe2e1 in __libc_global_ctors () at soinit.c:50
#4  0x400fe35b in init (argc=1, argv=0xbffffb1c, envp=0xbffffb24)
    at ../sysdeps/unix/sysv/linux/init-first.c:98
#5  0x4000e957 in call_init () at eval.c:41
#6  0x4000ea7e in _dl_init () at eval.c:41

is that stack trace even correct?

gnu find segfaults at the same place...  so far those are the only two
programs that I've had problems with.

this happens with glibc 2.2.2 compiled by either gcc 2.95.3-prerelease4 or
a snapshot of the 2/22/01 gcc cvs.

Any ideas?


justin
-- 
I see dead people.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]