I used LD_DEBUG=all ./app but nothing was shown at all.
Investigating the code shows that this functionality is disabled for __mips__ 
anyway.
... snip from dl-string.h

/* The following macros may be used in dl-startup.c to debug

* ldso before ldso has fixed itself up to make function calls */

/* On some (wierd) arches, none of this stuff works at all, so

* disable the whole lot... */

#if defined(__mips__)

# define SEND_STDERR(X)

# define SEND_ADDRESS_STDERR(X, add_a_newline)

# define SEND_NUMBER_STDERR(X, add_a_newline)

#else

... snap

 
Using gdbserver is not easy because I have to link it static. I will set up 
such debug environment
 
I hoped that someone has run into the same problem and has found the 
reason/workaroug for this.
 
Carsten
 

-----Ursprüngliche Nachricht-----
Von: Joakim Tjernlund [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 31. Mai 2007 23:31
An: Carsten Lange; [email protected]
Betreff: RE: segmentation fault of dynamic executables with ld-uClibc.so.0 
from0.9.29 on mipsel


Try enabling SUPPORT_LD_DEBUG and run:
LD_DEBUG=all ./app
 
you could try using gdb as well


  _____  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carsten Lange
Sent: den 31 maj 2007 11:02
To: [email protected]
Subject: segmentation fault of dynamic executables with ld-uClibc.so.0 
from0.9.29 on mipsel



Hi all, 
I used buildroot to build 3 toolchains for mipsel with different uClibc 
versions and same versions of binutils and gcc: 

binutils version 2.17
gcc version 4.1.2
kernel-headers 2.4.25
uClibc versions
0.9.28
0.9.28.3
0.9.29 
I discovered that dynamically linked executables do segfault when I use 0.9.29.
uClibc version 0.9.28 and 0.9.28.3 are working fine.
When I copy ld-uClibc.so.0 from uClibc version 0.9.28 and 0.9.28.3 onto the 
target replacing the ld-uClibc.so.0 from 0.9.29 everything works fine as well.

Any help is very much welcome! 
Carsten 




_______________________________________________
uClibc mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/uclibc

Reply via email to