On Tue, Oct 14, 2008 at 12:42:31PM +0800, Ming-Ching Tiew wrote: > >My app crashed in uClibc after running for about a week, >and this is the kernel dmesg log :- > ><6>my_app[5656]: segfault at fffffea0 ip b743a437 sp 0818ff04 >error 6 in libuClibc-0.9.28.so[b740e000+37000] > >Is there any suggestions for giving additional clues to the >crash ( perhaps the function calls stack ) ?
Run your app (perhaps via a screen session) in gdb and show us 'bt f'. Compile uClibc and your app with something like "-g3 -ggdb3" (refer to the documentation of your compiler). > >Since I have the sources to my_app and uclibc, I don't >mind recompile everything as long as it does not impact >performance to badly. As long as you don't build with optimizations disabled the speed should be about the same. > >Would 'sstrip' impact the capability to debug a library and >an app ? yes, strip -d (and sstrip for that matter) will remove debug information. You didn't say which version of uClibc you use on which arch, nor if your app uses threads etc. _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
