JDK-8036003: Add variable not to separate debug information. (original) (raw)

Daniel D. Daugherty daniel.daugherty at oracle.com
Tue Mar 4 03:02:34 UTC 2014

On 3/3/14 2:49 PM, Omair Majid wrote:

* David Holmes <david.holmes at oracle.com> [2014-02-28 18:48]:

There are three pieces to all of this:

1. Generating debug symbols in the binaries (via gcc -g or whatever) 2. Generating debuginfo files (zipped or not) (FDS) 3. Stripping debug symbols from the binaries (strip-policy) It may be that we don't have clean separation between them, and if so that should be fixed, but I don't see the current proposal as the way forward. Any chance we could clean up the names too? It's not obvious to me why FDS means 'generating debuginfo files'.

FDS stands for Full Debug Symbols and is defined that way in quite a few Makefiles... We just call it FDS for short...

What do folks think of modifying the OPENJDK build to use this as the settings for the options above by default.

1. Yes 2. No 3. No

Whatever we do here has be architecturallyconsistent across the various OpenJDK platforms. The above settings would not work well on non-Linux platforms so I'm not in favor of doing that.

However, I don't have a problem with providing support for config'ing a build to work with the downstream Linux repos...

Also there may well be differences between how things are handled on the JDK side and hotspot side. Is there any chance of this becoming consistent between hotspot and JDK? It would be much nicer if concepts like strip-policy were consistent between hotspot and the rest of the JDK.

When I did the Full Debug Symbols (FDS) project, I made it architecturally consistent between the HotSpot and JDK sides. Since the new build system has arrived, something of the consistency has been broken and I haven't been back on the JDK side to see what happened...

Dan

Thanks, Omair

More information about the core-libs-dev mailing list