Andrew Haley wrote:
Kelly O'Hair wrote:
Yes, I think you are right. Sorry, I think I sent you on this dead goose
chase. :^(
If this is in the jaxp and jaxws repositories, we need to fix those too.
Alright. I'll test a new patch and submit it here.
Part of the problem is, I think, that we took this discussion offline.
Agreed.
Andrew.
---
A little background...
With native code the historic position on debug has been between two extremes:
debug builds - full debug information
production builds - no debug information at all, and stripped ELF symbols
Functionality wise, everything worked fine in all cases.
But stripping out all the ELF symbols meant that a native stack trace would
only have the global exported function names, not a very helpful stack trace.
So we stopped stripping all the ELF symbols on most libraries so that a native
stack trace at least had all the native function names, on our jdk production
builds. Not sure how this lines up with common Linux conventions.
With Java code it has been my experience that having literally no debug
information in the class files just isn't very common, or helpful and
actually starts creeping into 'lost functionality' if the Java exceptions
don't provide source files names and line numbers.
I should have caught this issue, sorry.
-kto
