[Top][All Lists]

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


From: ragamuffin
Subject: None
Date: Mon, 9 Jun 2003 18:49:00 +0200


unfortunatly, since I updated glibc to versin 2.3.2 -
a lot af my app's crash on startup - gdb shows "recived
SEGV in strverscmp()" in all cases and I regconized that
all programs are linked against /lib/libpthread.so.0 -
which is now version 0.10 and was 0.9 before.
i'm now convinced that its a pthread problem - since
this conftest.c failed as i wanted to update gtk (which
i suspected before).

=====begin conftest.c=========
 #include <pthread.h>
 int check_me = 0;
 void* func(void* data) {check_me = 42; return &check_me;}
 int main()
  { pthread_t t;
    void *ret;
    pthread_create (&t, 0, func, 0);
    pthread_join (t, &ret);
    exit (check_me != 42 || ret != &check_me);

====gdb conftest.c============
Starting program: /mnt/software/glib/dummy 
[New Thread 16384 (LWP 4987)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 4987)]
0x400e365d in strverscmp () from /lib/libc.so.6

..not more unfortunately - and it takes another day to
compile glibc an my 350MHz K6 - so where's the bug here ?
how do I ensure it works next recompile (gcc 3.3 btw.) ?
could I decompile code at 0x400e365d somehow ?

I compiled that with a staticly linked gcc btw., cause
last time I updated the glibc, same thing happend
and I thought it's probably got to do with that
old (2.2.1) glibc was compiled with gcc 2.95 and progs
linked against that are unhappy to become runtime-linked
againt 3.3-compiled new version.

help a little


reply via email to

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