Hi Leonid,
2016-01-16 11:13 GMT+02:00 Leonid Lisovskiy <lly.dev(a)gmail.com>om>:
Please check presence of full line information in
debug sections:
readelf -WS /opt/lib/openjdk8/arm/libnet.so | grep .debug_macinfo
It's not there, indeed:
[root@unknown root]$ readelf -WS
/opt/lib/openjdk8/arm/libnet.so | grep .debug_macinfo
[root@unknown root]$
Have you tried addr2line method?
No, but seeing full line information isn't there, it seems there's no
sense too.
Which gcc version you are using? Could it be
optimization issues? Will
something changed if build OpenJDK without compiler optimizations, gcc
flag "-O0" (disable -Os/-O2) ?
I'm using gcc-5.2.0. I haven't tried "-O0" flag, and I remember I used
to debug some applications with "-O2" built with the same toolchain
and '-g' flag, and they had line information. I've now noticed I have
"--disable-debug-symbols" and "--disable-zip-debug-info" in OpenJDK
configure options, maybe it's filtering out the '-g3' option I added
manually? I should try to disable those options.
I am still missing your info, when does the failure occurs.
On startup? Can you also put up a complete strace log from
the ARM soft-float system. So I can compare.
And may be you try with just my OpenJDK8 patch and verify, that
it is not another change in your used patches....
best regards
Waldemar