Thank you.
On Thu, Dec 15, 2016 at 3:16 PM, Erik Joelsson
wrote:
> That is the intention.
>
> /Erik
>
> On 2016-12-15 14:57, Thomas Stüfe wrote:
>
> Hi Erik,
>
> great, thank you!
>
> So, for the gtest libjvm the binary would always contain internal debug
> symbols and
That is the intention.
/Erik
On 2016-12-15 14:57, Thomas Stüfe wrote:
Hi Erik,
great, thank you!
So, for the gtest libjvm the binary would always contain internal
debug symbols and we would not generate debuginfo files, right?
Thomas
On Thu, Dec 15, 2016 at 2:55 PM, Erik Joelsson
Hi Erik,
great, thank you!
So, for the gtest libjvm the binary would always contain internal debug
symbols and we would not generate debuginfo files, right?
Thomas
On Thu, Dec 15, 2016 at 2:55 PM, Erik Joelsson
wrote:
> Filed
Filed https://bugs.openjdk.java.net/browse/JDK-8171310 and working on it.
/Erik
On 2016-12-15 14:37, Erik Joelsson wrote:
Hello,
That is a mistake in JDK-8150736. My intention was to always leave
debug symbols in the gtest libjvm.so untouched.
/Erik
On 2016-12-15 14:13, Thomas Stüfe
Hello,
That is a mistake in JDK-8150736. My intention was to always leave debug
symbols in the gtest libjvm.so untouched.
/Erik
On 2016-12-15 14:13, Thomas Stüfe wrote:
Hi,
I may be missing something very obvious, but I am not able to debug the
gtest-libjvm (the one gtestLauncher uses,
Hi,
I may be missing something very obvious, but I am not able to debug the
gtest-libjvm (the one gtestLauncher uses, from
hotspot/variant-server/libjvm).
I build with --with-native-debug-symbols=external
--with-debug-level=slowdebug.
In the build log I see that we preserve the debug