Any support for not stripping binaries?

[David Holmes]

On 15/03/2013 9:46 AM, Omair Majid wrote:
> Hi,
>
> I was wondering if there a known way to avoid stripping binaries?
>
> I tried the following configuration
> $ bash configure --enable-debug --disable-zip-debug-info
> $ make POST_STRIP_CMD='' STRIP_POLICY=no_strip DEBUG_BINARIES=true all
>
> The hotspot shared objects (such as libjvm.so, libjsgi.so, libattach.so)
> still had DWARF information, but all JDK shared objects (such as the
> java launcher, libawt.so) seem to be stripped.
>
> Is there a way to emulate this style of the builds?
>
> $ make
>    DEBUG_CLASSFILES="true" \
>    DEBUG_BINARIES="true" \
>    STRIP_POLICY="no_strip"

It appears not. STRIP_POLICY is not used on the jdk side of the build 
any more (why? accidental omission in the conversion?) - though I found 
it somewhat dubious anyway. There's a tension between what to put in in 
the first place, versus what to strip out later. Eg creating libs with 
all symbols can be useful for debugging, but the final image can have 
them stripped out. Problem then is that you need vastly more disk space 
during the build.

Given that POST_STRIP_COMMAND= on the make invocation should nullify 
post-stripping, I'm wondering if the problem is with what is getting 
built in in the first place?

And as you note hotspot deals with this it's own, potentially 
incompatible, way.

David
-----

> Thanks,
> Omair
>