Fail to debug openjdk7 with gdb
john.cuthbertson at oracle.com
Thu Nov 3 09:47:28 PDT 2011
The Hotspot JVM uses certain signals for it's own use and SIGSEGV is one
such signal. The code below is generating the signal to act as a pseudo
memory barrier. SIGSEGV can also generated by JIT generated code as a
null check. To continue debugging use the gdb command:
> handle SIGSEGV nostop noprint
I think the other signals the JVM can legitimately generate are SIGBUS
Hope this helps.
On 11/03/11 08:56, Lokesh Gidra wrote:
> I am trying to debug openjdk7 using gdb, and everytime it fails with
> the following trace:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffe1df7700 (LWP 14211)]
> 0x00007ffff634bf60 in os::write_memory_serialize_page
> 319 *(volatile int32_t
> *)((uintptr_t)_mem_serialize_page+page_offset) = 1;
> Running the same build without gdb works fine. Also, there are no
> changes made by me. The code is freshly downloaded from the website.
> Can someone please point out what could be going wrong.
> Thanks in advance,
> Best Regards,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-gc-dev