This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
[Felipe Contreras <al593181@mail.mty.itesm.mx>] bug in useldt.h
- From: Andreas Jaeger <aj at suse dot de>
- To: libc-alpha at sources dot redhat dot com
- Cc: Felipe Contreras <al593181 at mail dot mty dot itesm dot mx>
- Date: Fri, 07 Dec 2001 14:50:38 +0100
- Subject: [Felipe Contreras <al593181@mail.mty.itesm.mx>] bug in useldt.h
Hi glibc developers,
has anybody an idea what might be the problem?
Felipe reports:
> The program that failed: int main() { return 0; }
>
> Compiled with: gcc tmp.c -o tmp -lpthread
He's using a selfcompiled glibc that and using the i686 LDT thread
implementation.
I can't reproduce this with current CVS sources. Can anybody else
reproduce this or has anybody an idea what might be the problem?
Andreas
--- Begin Message ---
Topics:
Re: bug in useldt.h
Re: bug in useldt.h
--- End Message ---
--- Begin Message ---
- From: Felipe Contreras <al593181 at mail dot mty dot itesm dot mx>
- To: bug-glibc at gnu dot org
- Date: Wed, 5 Dec 2001 20:37:01 -0600
- Subject: Re: bug in useldt.h
- References: <20011205054432.GA378@sion.sytes.net><u8r8qanlor.fsf@gromit.moeb> <20011205093734.GA9493@sion.sytes.net><hoitbm800i.fsf@gee.suse.de>
I debuged the 'ls' that segfaults
The message:
============
0x4015954a in __pthread_alt_lock () from /lib/libpthread.so.0
The segfault comes here:
========================
0x4015954a <__pthread_alt_lock+26>: mov %gs:0x0,%eax
The gs register:
================
gs 0x0 0
The backtrace:
==============
#0 0x4015954a in __pthread_alt_lock () from /lib/libpthread.so.0
#1 0x401568d5 in pthread_mutex_lock () from /lib/libpthread.so.0
#2 0x4012ae23 in __register_frame_info (begin=0x40014c94, ob=0x0)
at ../../gcc-2.95.3/gcc/frame.c:627
#3 0x400466c2 in init () from /lib/libc.so.6
#4 0x4000b797 in call_init () from /lib/ld-linux.so.2
#5 0x4000b8ee in _dl_init () from /lib/ld-linux.so.2
After that I remember I saw programs segfaulting only when they were linked to
'rt' and 'pthread', so I did a simple test program and compiled against those
libraries and it segfaulted.
After some tries linking with some libraries I found that the problem comes
when compiling against 'pthread'.
The program that failed: int main() { return 0; }
Compiled with: gcc tmp.c -o tmp -lpthread
Debugging it I found the same results. It runs on my normal system, but with
the new glibc it segfaults.
When runing the testsuite some tests failed, and all of the tests in
libpthreads failed.
_______________________________________________
Bug-glibc mailing list
Bug-glibc@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-glibc
--- End Message ---
--- Begin Message ---
- From: Felipe Contreras <al593181 at mail dot mty dot itesm dot mx>
- To: Andreas Jaeger <aj at suse dot de>
- Cc: bug-glibc at gnu dot org
- Date: Thu, 6 Dec 2001 14:35:30 -0600
- Subject: Re: bug in useldt.h
- References: <20011205054432.GA378@sion.sytes.net><u8r8qanlor.fsf@gromit.moeb> <20011205093734.GA9493@sion.sytes.net><hoitbm800i.fsf@gee.suse.de> <20011206023701.GA219@sion.sytes.net><u8snao95yo.fsf@gromit.moeb>
On Thu, Dec 06, 2001 at 08:13:19AM +0100, Andreas Jaeger wrote:
>
> Which Linux kernel are you using?
I tried it with 2.4.16 and 2.4.17-pre2. And I remember this happening
with other kernels.
>
> Since you recompiled glibc yourself, did you run the testsuite with
> make check?
Yes, make check.
--- End Message ---
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj