本文主要是介绍JNI调用本地库时JAVA虚拟机异常退出问题定位,通过虚拟机生成的hs_err_pidxxx.log日志文件定位过程,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!
JAVA代码中有一处需要通过JNI调用本地的DLL库,每次一到这里整个程序就直接闪退,程序目录下有生成的虚拟机日志文件hs_err_pidxxx.log,相同的程序运行在别的机器上都没有问题,刚开始无从下手。
1 开始慢慢分析hs_err_pidxxx.log文件,日志的第二行EXCEPTION_ACCESS_VIOLATION ,发生这样的错误,大多是JNI端代码有问题,如:不恰当的 printf 及 cout 调用,方法调用类型不兼容,调用被销毁的对象等。可是在别的机器上程序运行又都是正常的,说明JNI部分的C++代码应该也没问题
2 下面把注意力放到了msvcrt.dll这个文件上,在环境上搜了一下,msvcrt.dll这个文件有N多个,而且大小各不相同,这里开始怀疑是不是动态库加载的顺序出了问题,接着发现这台电脑上安装了多个版本的程序,其中的JDK库和程序自己的相关DLL库文件都不一样。
3 之后把程序的path路径修改了一下,把程序自己的DLL目录放在了最前面,重新运行程序,一切正常了。
hs_err_pidxxx.log文件开始
----------------------------------------------------------------------------------------------------------------------------------------------------
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x77c17a6f, pid=6528, tid=6772
#
# JRE version: 6.0_18-b07
# Java VM: Java HotSpot(TM) Client VM (16.0-b13 mixed mode windows-x86 )
# Problematic frame:
# C [msvcrt.dll+0x37a6f]
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--------------- T H R E A D ---------------
Current thread (0x0323d400): JavaThread "AWT-EventQueue-0" [_thread_in_native, id=6772, stack(0x04140000,0x04190000)]
siginfo: ExceptionCode=0xc0000005, reading address 0x00000000
Registers:
EAX=0x00000000, EBX=0x00000004, ECX=0x00000004, EDX=0x04148bdc
ESP=0x04148ba8, EBP=0x04148bb4, ESI=0x00000000, EDI=0x04148bdc
EIP=0x77c17a6f, EFLAGS=0x00010202
Top of Stack: (sp=0x04148ba8)
0x04148ba8: 003fa8a8 00000000 080c2e61 003fa7b0
0x04148bb8: 08071846 04148bdc 00000000 00000004
0x04148bc8: 04148d84 00000003 04148d84 003f9c38
0x04148bd8: 0804566b 6d783f3c 00000000 04148d84
0x04148be8: 04148d84 003f9c38 0807280d 003f9c38
0x04148bf8: 04148d84 04148d84 00000000 04148d84
0x04148c08: 0000002c 080728be 04148d84 00000000
0x04148c18: 003f9c38 003f9c38 0803493c 04148d84
Instructions: (pc=0x77c17a6f)
0x77c17a5f: 08 8b f7 33 c0 f2 ae f7 d9 03 cb 8b fe 8b 75 0c
0x77c17a6f: f3 a6 8a 46 ff 33 c9 3a 47 ff 77 04 74 04 49 49
Stack: [0x04140000,0x04190000], sp=0x04148ba8, free space=22041486dck
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [msvcrt.dll+0x37a6f]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j com.zte.ums.zxwomc.tools.trace.wsf.comm.st.decode.SignalDecode3G.SignalDecodeNesting(Lcom/zte/ums/zxwomc/tools/trace/wsf/decode/DllRetInfo;[BISSIILjava/lang/String;III)[B+0
j com.zte.ums.zxwomc.tools.trace.wsf.comm.st.decode.SignalDecode3G.M3UA([BII)[B+34
j com.zte.ums.zxwomc.tools.trace.wsf.comm.st.frame.M3uaXmlDecodingProcessor.getDetails(ZLjava/lang/Object;)Ljava/lang/String;+102
j com.zte.ums.zxwomc.tools.trace.wsf.decode.xml.XmlDecodingPanel.fillMsgDetails(Lcom/zte/ums/zxwomc/tools/trace/wsf/decode/comm/ResultObj;)V+33
j com.zte.ums.zxwomc.tools.trace.wsf.comm.st.frame.M3UATraceFrame.updateDetailUI(Lcom/zte/ums/zxwomc/tools/trace/wsf/main/MsgInfo;)V+90
j com.zte.ums.zxwomc.tools.trace.wsf.frame.TraceFrame.codeView_actionPerformed()V+273
j com.zte.ums.zxwomc.tools.trace.wsf.frame.TraceFrame$5.mouseReleased(Ljava/awt/event/MouseEvent;)V+152
j java.awt.AWTEventMulticaster.mouseReleased(Ljava/awt/event/MouseEvent;)V+21
j java.awt.Component.processMouseEvent(Ljava/awt/event/MouseEvent;)V+64
j javax.swing.JComponent.processMouseEvent(Ljava/awt/event/MouseEvent;)V+23
J java.awt.Component.processEvent(Ljava/awt/AWTEvent;)V
J java.awt.Container.processEvent(Ljava/awt/AWTEvent;)V
J java.awt.Component.dispatchEventImpl(Ljava/awt/AWTEvent;)V
J java.awt.Container.dispatchEventImpl(Ljava/awt/AWTEvent;)V
J java.awt.LightweightDispatcher.retargetMouseEvent(Ljava/awt/Component;ILjava/awt/event/MouseEvent;)V
J java.awt.LightweightDispatcher.processMouseEvent(Ljava/awt/event/MouseEvent;)Z
J java.awt.LightweightDispatcher.dispatchEvent(Ljava/awt/AWTEvent;)Z
J java.awt.Container.dispatchEventImpl(Ljava/awt/AWTEvent;)V
J java.awt.Window.dispatchEventImpl(Ljava/awt/AWTEvent;)V
J java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V
J java.awt.EventDispatchThread.pumpOneEventForFilters(I)Z
j java.awt.EventDispatchThread.pumpEventsForFilter(ILjava/awt/Conditional;Ljava/awt/EventFilter;)V+30
j java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+11
j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)
这篇关于JNI调用本地库时JAVA虚拟机异常退出问题定位,通过虚拟机生成的hs_err_pidxxx.log日志文件定位过程的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!