I don't think I had any issues with symbol resolution and stack unwinding
with the default fastdebug build (provided that the frame pointers are
preserved).
Can anyone shed some light on what the benefits of
--with-native-debug-symbols=internal are?
On Mon, 20 Nov 2017, 21:56 John Hening,
>
> With perf. OpenJDK might need to be configured with debug symbols:
> --with-native-debug-symbols=internal
>
@Aleksey, when I try to configure openjdk8 with that option I get an error:
configure: error: unrecognized options: --with-native-debug-symbols
Exactly, I I downloaded jdk8u and I
On 11/18/2017 01:45 PM, John Hening wrote:
> Thanks for your replies :)
>
> @Aleksey, how to get that?
>
> |-17.12%0.00%org.openjdk.Allperf-31615.map-0x7faaa3b2d125-16.59%OptoRuntime::new_instance_C
> -11.49%InstanceKlass::allocate_instance
> 2.33%BlahBlahBlahCollectedHeap::mem_allocate
Thanks for your replies :)
@Aleksey, how to get that?
- 17.12% 0.00% org.openjdk.All perf-31615.map
- 0x7faaa3b2d125
- 16.59% OptoRuntime::new_instance_C
- 11.49% InstanceKlass::allocate_instance
2.33% BlahBlahBlahCollectedHeap::mem_allocate < entry
On 11/17/2017 11:46 PM, John Hening wrote:
> For my eye, common objects in Java, like
>
> newString();
>
> is a CHeapObj. I looked at an implementation of new operator in that class
> and it looks like:
In related news, there is javaClasses.cpp, and therefore Java class library is
written in
I am reading source of HotSpot sourcode src/share/vm/memory/allocation.hpp
and I see:
// All classes in the virtual machine must be subclassed
> // by one of the following allocation classes:
> //
> // For objects allocated in the resource area (see resourceArea.hpp).
> // - ResourceObj
> //
>
