https://bugzilla.novell.com/show_bug.cgi?id=194711 ------- Comment #64 from bugproxy@us.ibm.com 2007-02-16 12:50 MST ------- ----- Additional Comments From suzukikp@in.ibm.com (prefers email at suzuki@in.ibm.com) 2007-02-16 14:47 EDT ------- Ok. I have enough information why we are getting the ld-linux.so as the file for dl-addr. In the failing case, the map for libjvm.so lies within the map for ld-linux.so. And while searching for the address, the ld-linux.so is consulted before the libjvm.so which hits the success for dl-addr and we end up doing something wrong. here is the o/p with the normal working case : (the map addresses are at the time of dl-addr calls ) ld - (0x2b12ab112000 - 0x2b12ab32fda8) - (size of ld-linux = 21DDA8 ) jvm.so(0x2b12ac10d000 - 0x2b12ac220018) We can see that jvm.so lies outside the ld limits. failing case : ld - (0x2b09214a9000 - 0x2b09216c6da8) - (size of ld-linux = 21DDA8 ) jvm.so(0x2b09214ed000 - 0x2b0921600018) - fail Here the jvm.so is still within the map of ld-linux !! So, this is causing the problem. The relocation is not happening properly for the failing case ! Debugging further. Thanks Suzuki -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.