libc.so.0 is linked to "libuClibc-0.9.30.so". I believe "ld-uClibc.so.0" is uClibc's dynamic linker. In the traces, that file is not being opened, just stat'ed.
Thank you for the patch suggestion, but it did not change the behaviour in this case. Now also I am less sure about the relationship to shared libraries, as this would not explain why simply touching the executable helps. Touch doesn't run the program, nor does it load any of the program's shared libraries, so I am not sure what it is doing to fix it; or what it is fixing, for that matter. Derek On Wed, Apr 22, 2009 at 1:46 AM, <[email protected]> wrote: > Derek Spadaro: >> It does. In this system /lib/libc.so.0 is symbolically linked to uClibc. >> lrwxrwxrwx 1 root root 19 Apr 22 2009 libc.so.0 -> >> libuClibc-0.9.30.so >> -rwxr-xr-x 1 root root 710040 Mar 23 2009 libuClibc-0.9.30.so > > But your strace shows /lib/libc.so.0 and /lib/ld-uClibc.so.0 are > different from each other. > I hope it is unrelated to this problem. > > open("/lib/libc.so.0", O_RDONLY) = 3 > fstat(3, {st_mode=S_IFREG|0755, st_size=710040, ...}) = 0 > ::: > stat("/lib/ld-uClibc.so.0", {st_mode=S_IFREG|0755, st_size=43176, ...}) = 0 > > >> This worked fine after touching the application only. It fails if >> that touch is omitted. Strace of the two cases is attached. > > While I am not sure, this problem may be related to the bug which was > reported by Matthew Harrell recently. Would you test this patch I have > sent to him? Of cource, he reported me it worked. > > > J. R. Okajima > > ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p
