my java application crash with coredump
coredump say terminated with signal 6 but hs_err_pid file was different:
it makes me confused
SIGSEGV is caught and handled by the JVM itself.
In response to SEGSEGV JVM writes hs_err_pid.log and then terminates process with abort() call to force core dump. abort() call results in SIGABRT.
Related
I have been developing a game in c++ using vulkan and moltenVK for porting to iOS and Mac. The game works fine when I run it through XCode on my iPhone, but when I distribute the app through TestFlight, it crashes immediately. Here is some of the crash report
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000048
Exception Codes: 0x0000000000000001, 0x0000000000000048
VM Region Info: 0x48 is not in any region. Bytes before following region: 4367466424
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 104524000-104798000 [ 2512K] r-x/r-x SM=COW ...ons And Mania
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: SIGNAL 11 Segmentation fault: 11
Terminating Process: exc handler [5132]
And the stack trace points to the first time my program calls MVKBuffer::MVKBuffer() via vkCreateBuffer.
I've verified that the build works when running from my machine, it's only when I build for a generic iOS device (arm64) and distribute through the app store that this is a problem.
Any idea why I would get a segfault when creating buffers?
I'm running into a strange intermittent bug on a game I'm developing for iOS and macOS using SpriteKit. After launching on the Mac and waiting some random amount of time, the game window starts flickering (see below) and I start getting the following console errors:
2016-10-20 12:52:43.000352 RobotGame-macOS[27086:790757] Execution of the command buffer was aborted due to an error during execution. <private>
2016-10-20 12:52:43.000432 RobotGame-macOS[27086:790757] Execution of the command buffer was aborted due to an error during execution. <private>
2016-10-20 12:52:57.139097 RobotGame-macOS[27086:790803] Execution of the command buffer was aborted due to an error during execution. <private>
2016-10-20 12:52:57.139173 RobotGame-macOS[27086:790803] Execution of the command buffer was aborted due to an error during execution. <private>
I've currently designed all the graphics using basic SpriteKit SKNodes with no other custom shaders or any other advanced Metal stuff.
So what is causing this? I don't know where to begin with debugging it.
I'm trying to Download attachments from Lotus notes, but JVM Crashes with this error:
EXCEPTION_ACCESS_VIOLATION (0xc0000005)
Problematic frame:
C [NLNVP.DLL]
Crash is cause by this method from Domino library:
extractFile(path);
once it hits this line, JVM goes down.
Any idea what's going on?
Remove line NLNVP.DLL from notes.ini and try to execute it will not crash the JVM
you (developer) and end user have same symantic version then JVM will not crash.
we are using NIOFSDirectory instead of MMapDirectory in an intensive test load for indexing. But we are still getting a SIGSEV with MMapDirectory. Is there anything else I should be looking for? This is a Linux 64 bit machine. Head of the stack trace follows:
Please let me know what more info would be helpful.
Thanks...
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00002aaaab285ea7, pid=2408, tid=1128642880
JRE version: 6.0_25-b06
Java VM: Java HotSpot(TM) 64-Bit Server VM (20.0-b11 mixed mode linux-amd64 compressed >oops)
Problematic frame:
J org.apache.lucene.store.MMapDirectory$MMapIndexInput.readByte()B
You are most likely closing your IndexReader while other threads are still using it?
Lucene tries to catch this mis-use but it's detection is best-effort only.
You could also try calling MMapDirectory.setUseUnmap(false) to turn off unmapping; this should prevent the SIGSEGV.
I have written a jvmti agent to trace method invocations. I code it with C and jvmti and jni functions. Our os is Fedora 15 and the agent is compiled into a .so file. When I test it with a non-trivial java program, it crashes and gives the following error message:
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x4e8e4e28, pid=24294, tid=3065949040.
JRE version: 6.0_32-b05.
Java VM: Java HotSpot (TM) Server VM (20.7-b02 mixed mode linux-x86).
**Problematic frame:
C [libc.so.6+0x7ae68] strcpy+0x18.**
IGSEGV is an abbreviation for Signal Segmentation Violation. On
POSIX-compliant platforms, SIGSEGV is the signal sent to a process
when it makes an invalid memory reference, or segmentation fault.
You have to check the pointers in your JVMTI agent. In all probability you make some unclean pointer operations.