Rob Landley wrote: > On Friday 01 June 2007 6:07 am, Carmelo AMOROSO wrote: >> Why do you need to link it statically if the problem seems to be in ld.so? > > Because if gdbserver is not linked statically, it needs ld.so to run, and > ld.so is segfaulting? > > This is just a guess. > > Rob Yes, you're right; in this case I could suggest this alternative way, using a mixed glibc/uClibc target.
Install the uClibc libs into a non default path into the target (for example /uClibc/lib) Build the application adding the following -Wl,--dynamic-linker,/uClibc/lib/ld-uClibc.so.0 Debug the application using the gdbserver (glibc linked) as usual Run the gdb client passing the ld-uClibc.so.0 image. This worked for me, at the beginning stage of the development when I did not have a working uClibc target Carmelo > _______________________________________________ > uClibc mailing list > [email protected] > http://busybox.net/cgi-bin/mailman/listinfo/uclibc > _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
