This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Compiler problem?
On Thu, Aug 16, 2001 at 09:32:19PM +1000, Greg Schafer wrote:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1024 (LWP 4013)]
> __pthread_alt_lock (lock=0x40148a74, self=0x0) at spinlock.c:440
> 440 do {
> (gdb) bt
> #0 __pthread_alt_lock (lock=0x40148a74, self=0x0) at spinlock.c:440
> #1 0x401578f5 in __pthread_mutex_lock (mutex=0x40148a64) at mutex.c:120
> #2 0x4012c248 in __register_frame_info (begin=0x40148b64, ob=0x4014b2e0) at ../../gcc-2.95.3/gcc/frame.c:627
> #3 0x4004761e in __libc_global_ctors () at soinit.c:50
> #4 0x400476c2 in init (argc=1, argv=0xbffffe34, envp=0xbffffe3c) at ../sysdeps/unix/sysv/linux/init-first.c:103
> #5 0x4000b797 in call_init (l=0x400152f0, argc=1, argv=0xbffffe34, env=0xbffffe3c) at dl-init.c:70
> #6 0x4000b8ee in _dl_init (main_map=0x40014cb8, argc=1, argv=0xbffffe34, env=0xbffffe3c) at dl-init.c:141
Ok, after a bit of research, this problem has come up before.
Problem was caused by me using "--enable-kernel=current" which
enabled the LDT thread stuff which seems to get compiled
incorrectly with my compiler (gcc-2.95.3 + patches).
Regards
Greg