Java 优化器导致的段故障

Java 优化器导致的段故障,java,curl,gdb,xml-rpc,Java,Curl,Gdb,Xml Rpc,我们在使用gdb跟踪日志时遇到了一个问题 .XMLRPC调用和gdb回溯显示时系统崩溃: Program terminated with signal 11, Segmentation fault. #0 finishCurlMulti (envP=0x0, curlMultiP=0xe37b800, timeoutType=timeout_no, deadline=..., interruptP=0x0) at xmlrpc_curl_transport.c:572 warnin

我们在使用gdb跟踪日志时遇到了一个问题 .XMLRPC调用和gdb回溯显示时系统崩溃:

Program terminated with signal 11, Segmentation fault.
#0  finishCurlMulti (envP=0x0, curlMultiP=0xe37b800, timeoutType=timeout_no, 
    deadline=..., interruptP=0x0) at xmlrpc_curl_transport.c:572

warning: Source file is more recent than executable.
572
(gdb) bt
#0  finishCurlMulti (envP=0x0, curlMultiP=0xe37b800, timeoutType=timeout_no, 
    deadline=..., interruptP=0x0) at xmlrpc_curl_transport.c:572
#1  0x00002b84f0b4ad24 in performCurlTransaction (envP=0x46a185d0, 
    clientTransportP=0xe365d50, serverP=<value optimized out>, 
    callXmlP=<value optimized out>, responseXmlPP=0x46a185e8)
    at xmlrpc_curl_transport.c:1036
#2  performRpc (envP=0x46a185d0, clientTransportP=0xe365d50, 
    serverP=<value optimized out>, callXmlP=<value optimized out>, 
    responseXmlPP=0x46a185e8) at xmlrpc_curl_transport.c:1141
#3  call (envP=0x46a185d0, clientTransportP=0xe365d50, 
    serverP=<value optimized out>, callXmlP=<value optimized out>, 
    responseXmlPP=0x46a185e8) at xmlrpc_curl_transport.c:1362
程序以信号11终止,分段故障。
#0 finishCurlMulti(envP=0x0,curlMultiP=0xe37b800,timeoutType=timeout_no,
在xmlrpc_curl_传输上的截止期=…,interruptP=0x0)。c:572
警告:源文件比可执行文件更新。
572
(gdb)英国电信
#0 finishCurlMulti(envP=0x0,curlMultiP=0xe37b800,timeoutType=timeout_no,
在xmlrpc_curl_传输上的截止期=…,interruptP=0x0)。c:572
#performCurlTransaction中的1 0x00002b84f0b4ad24(envP=0x46a185d0,
clientTransportP=0xe365d50,serverP=,
callXmlP=,responseXmlPP=0x46a185e8)
在xmlrpc_curl_transport.c:1036
#2个performRpc(envP=0x46a185d0,clientTransportP=0xe365d50,
serverP=,callXmlP=,
xmlrpc_curl_transport上的responseXmlPP=0x46a185e8)。c:1141
#3调用(envP=0x46a185d0,clientTransportP=0xe365d50,
serverP=,callXmlP=,
xmlrpc_curl_transport上的responseXmlPP=0x46a185e8)。c:1362
=>是否存在空指针错误?envP=0x0

-------------------------------------跟踪帧1--------------------

(gdb) frame 1
#1  0x00002b84f0b4ad24 in performCurlTransaction (envP=0x46a185d0, clientTransportP=0xe365d50, serverP=<value optimized out>, callXmlP=<value optimized out>, 
    responseXmlPP=0x46a185e8) at xmlrpc_curl_transport.c:1036
1036               synchronous RPC can be in progress is for the 'perform' method
(gdb) print envP
$1 = <value optimized out>
(gdb) info registers
rax            0x0      0
rbx            0xec59270        247829104
rcx            0x0      0
rdx            0x2      2
rsi            0x46a18200       1184989696
rdi            0xe37b800        238532608
rbp            0x46a185d0       0x46a185d0
rsp            0x46a184e0       0x46a184e0
r8             0x46a17f00       1184988928
r9             0x46a17ef0       1184988912
r10            0x46a18100       1184989440
r11            0x206    518
r12            0xe365d50        238443856
r13            0xe37b800        238532608
r14            0xe99dda0        244964768
r15            0x46a185e8       1184990696
rip            0x2b84f0b4ad24   0x2b84f0b4ad24 <call+340>
eflags         0x10206  [ PF IF RF ]
cs             0x33     51
ss             0xe02b   57387
ds             0x0      0
es             0x0      0
fs             0x63     99
gs             0x0      0
fctrl          0x37f    895
fstat          0x0      0
ftag           0xffff   65535
fiseg          0x0      0
fioff          0x0      0
foseg          0x0      0
fooff          0x0      0
fop            0x0      0
mxcsr          0x1fa0   [ PE IM DM ZM OM UM PM ]
(gdb) frame 0
#0  finishCurlMulti (envP=0x0, curlMultiP=0xe37b800, timeoutType=timeout_no, deadline=..., interruptP=0x0) at xmlrpc_curl_transport.c:572
572
(gdb) print envP
$2 = (xmlrpc_env * const) 0x0
(gdb) info register
rax            0x0      0
rbx            0x0      0
rcx            0x0      0
rdx            0x2      2
rsi            0x46a18200       1184989696
rdi            0xe37b800        238532608
rbp            0xe37b800        0xe37b800
rsp            0x46a182f0       0x46a182f0
r8             0x46a17f00       1184988928
r9             0x46a17ef0       1184988912
r10            0x46a18100       1184989440
r11            0x206    518
r12            0x0      0
r13            0x0      0
r14            0x0      0
r15            0x0      0
rip            0x2b84f0b49e93   0x2b84f0b49e93 <finishCurlMulti+259>
eflags         0x10206  [ PF IF RF ]
cs             0x33     51
ss             0xe02b   57387
ds             0x0      0
es             0x0      0
fs             0x63     99
gs             0x0      0
fctrl          0x37f    895
fstat          0x0      0
ftag           0xffff   65535
fiseg          0x0      0
fioff          0x0      0
foseg          0x0      0
fooff          0x0      0
fop            0x0      0
mxcsr          0x1fa0   [ PE IM DM ZM OM UM PM ]
(gdb)第1帧
#performCurlTransaction中的1 0x00002b84f0b4ad24(envP=0x46a185d0,clientTransportP=0xe365d50,serverP=,callXmlP=,
xmlrpc_curl_transport上的responseXmlPP=0x46a185e8)。c:1036
1036“执行”方法的同步RPC可能正在进行中
(gdb)打印环境
$1 = 
(gdb)信息寄存器
rax 0x0 0
rbx 0xec59270 247829104
rcx 0x0 0
rdx 0x2
rsi 0x46a18200 1184989696
rdi 0xe37b800 238532608
rbp 0x46a185d0 0x46a185d0
rsp 0x46a184e0 0x46a184e0
r8 0x46a17f00 1184988928
r9 0x46a17ef0 1184988912
r10 0x46a18100 1184989440
r11 0x206 518
r12 0xe365d50 238443856
r13 0xe37b800 238532608
r14 0xe99dda0 244964768
r15 0x46a185e8 1184990696
rip 0x2b84f0b4ad24 0x2b84f0b4ad24
eflags 0x10206[PF IF RF]
cs 0x33 51
不锈钢0xe02b 57387
ds 0x0 0
es 0x0 0
fs 0x63 99
gs 0x0 0
fctrl 0x37f 895
fstat0x0
ftag 0xffff 65535
fiseg 0x0 0
fioff 0x0 0
foseg 0x0 0
fooff 0x0 0
fop 0x0 0
mxcsr 0x1fa0[PE IM DM ZM OM UM PM]
=======>envP是否存储在寄存器rbp中

------------------------返回到第0帧-------------------

(gdb) frame 1
#1  0x00002b84f0b4ad24 in performCurlTransaction (envP=0x46a185d0, clientTransportP=0xe365d50, serverP=<value optimized out>, callXmlP=<value optimized out>, 
    responseXmlPP=0x46a185e8) at xmlrpc_curl_transport.c:1036
1036               synchronous RPC can be in progress is for the 'perform' method
(gdb) print envP
$1 = <value optimized out>
(gdb) info registers
rax            0x0      0
rbx            0xec59270        247829104
rcx            0x0      0
rdx            0x2      2
rsi            0x46a18200       1184989696
rdi            0xe37b800        238532608
rbp            0x46a185d0       0x46a185d0
rsp            0x46a184e0       0x46a184e0
r8             0x46a17f00       1184988928
r9             0x46a17ef0       1184988912
r10            0x46a18100       1184989440
r11            0x206    518
r12            0xe365d50        238443856
r13            0xe37b800        238532608
r14            0xe99dda0        244964768
r15            0x46a185e8       1184990696
rip            0x2b84f0b4ad24   0x2b84f0b4ad24 <call+340>
eflags         0x10206  [ PF IF RF ]
cs             0x33     51
ss             0xe02b   57387
ds             0x0      0
es             0x0      0
fs             0x63     99
gs             0x0      0
fctrl          0x37f    895
fstat          0x0      0
ftag           0xffff   65535
fiseg          0x0      0
fioff          0x0      0
foseg          0x0      0
fooff          0x0      0
fop            0x0      0
mxcsr          0x1fa0   [ PE IM DM ZM OM UM PM ]
(gdb) frame 0
#0  finishCurlMulti (envP=0x0, curlMultiP=0xe37b800, timeoutType=timeout_no, deadline=..., interruptP=0x0) at xmlrpc_curl_transport.c:572
572
(gdb) print envP
$2 = (xmlrpc_env * const) 0x0
(gdb) info register
rax            0x0      0
rbx            0x0      0
rcx            0x0      0
rdx            0x2      2
rsi            0x46a18200       1184989696
rdi            0xe37b800        238532608
rbp            0xe37b800        0xe37b800
rsp            0x46a182f0       0x46a182f0
r8             0x46a17f00       1184988928
r9             0x46a17ef0       1184988912
r10            0x46a18100       1184989440
r11            0x206    518
r12            0x0      0
r13            0x0      0
r14            0x0      0
r15            0x0      0
rip            0x2b84f0b49e93   0x2b84f0b49e93 <finishCurlMulti+259>
eflags         0x10206  [ PF IF RF ]
cs             0x33     51
ss             0xe02b   57387
ds             0x0      0
es             0x0      0
fs             0x63     99
gs             0x0      0
fctrl          0x37f    895
fstat          0x0      0
ftag           0xffff   65535
fiseg          0x0      0
fioff          0x0      0
foseg          0x0      0
fooff          0x0      0
fop            0x0      0
mxcsr          0x1fa0   [ PE IM DM ZM OM UM PM ]
(gdb)第0帧
#在xmlrpc_curl_传输上0 finishCurlMulti(envP=0x0,curlmultp=0xe37b800,timeoutType=timeout_no,deadline=…,interruptP=0x0)。c:572
572
(gdb)打印环境
$2=(xmlrpc_env*const)0x0
(gdb)信息登记册
rax 0x0 0
rbx 0x0 0
rcx 0x0 0
rdx 0x2
rsi 0x46a18200 1184989696
rdi 0xe37b800 238532608
rbp 0xe37b800 0xe37b800
rsp 0x46a182f0 0x46a182f0
r8 0x46a17f00 1184988928
r9 0x46a17ef0 1184988912
r10 0x46a18100 1184989440
r11 0x206 518
r12 0x0 0
r13 0x0 0
r14 0x0 0
r15 0x0 0
rip 0x2b84f0b49e93 0x2b84f0b49e93
eflags 0x10206[PF IF RF]
cs 0x33 51
不锈钢0xe02b 57387
ds 0x0 0
es 0x0 0
fs 0x63 99
gs 0x0 0
fctrl 0x37f 895
fstat0x0
ftag 0xffff 65535
fiseg 0x0 0
fioff 0x0 0
foseg 0x0 0
fooff 0x0 0
fop 0x0 0
mxcsr 0x1fa0[PE IM DM ZM OM UM PM]
=======>请告诉我这种情况有什么问题

我试图使用-O0禁用优化器,但我不确定

谢谢

这是我的回溯和正确的源文件:

#0  finishCurlMulti (envP=0x0, curlMultiP=0x12e2580, timeoutType=timeout_yes, deadline=..., interruptP=0x0) at xmlrpc_curl_transport.c:572
#1  0x00002abe7f51d0b4 in finishAsynch (clientTransportP=0x12e24c0, timeoutType=timeout_yes, timeout=10000) at xmlrpc_curl_transport.c:1301
#2  0x00002abe7f72f5c6 in xmlrpc_c::clientXmlTransport_http::finishAsync (this=0x12e2470, timeout=...) at client.cpp:624
#3  0x00002abe7f72f64a in xmlrpc_c::client_xml::finishAsync (this=0x1304bf0, timeout=...) at client.cpp:893
#4  0x00002aaaab57c26d in UrlStruct::runXmlRpc (this=0x122d140, method="mediacontrol.onEvent", paramList=<value optimized out>, result=<value optimized out>) at Utils.cpp:146
#5  0x00002aaaab57c526 in IVRUtils::executeXmlRpc (controllerUrl=0x12e2580, methodName=Traceback (most recent call last):   
#6  0x00002aaaab54366a in IvrCoreSession::_exec_xmlrpc_cmd (this=0x2aaab48277f0, paramList=..., result=0x41228cb0) at IvrCoreSession.cpp:307
#7  0x00002aaaab544c95 in IvrCoreSession::fireEndCallEvent (this=0x2aaab48277f0) at IvrCoreSession.cpp:504
#8  0x00002aaaab54752d in IvrCoreSession::~IvrCoreSession (this=0x2aaab48277f0, __in_chrg=<value optimized out>) at IvrCoreSession.cpp:101
#9  0x000000000047c15d in AmSessionContainer::clean_sessions (this=0x10cbdd0) at AmSessionContainer.cpp:94
#10 0x000000000047c898 in AmSessionContainer::run (this=0x10cbdd0) at AmSessionContainer.cpp:132
#11 0x000000000049266c in AmThread::_start (_t=<value optimized out>) at AmThread.cpp:70
#12 0x000000397ec0673d in start_thread () from /lib64/libpthread.so.0
#13 0x000000397e0d40cd in clone () from /lib64/libc.so.6 
在xmlrpc_curl_transport.c:572处0 finishCurlMulti(envP=0x0,curlmultp=0x12e2580,timeoutType=timeout_yes,deadline=…,interruptP=0x0) #1 0x00002abe7f51d0b4在xmlrpc_curl_transport处完成同步(clientTransportP=0x12e24c0,timeoutType=timeout_yes,timeout=10000)。c:1301 #客户端的xmlrpc_c::clientXmlTransport_http::finishAsync(this=0x12e2470,timeout=…)中的2 0x00002abe7f72f5c6。cpp:624 #客户端的xmlrpc_c::client_xml::finishAsync(this=0x1304bf0,timeout=…)中的0x00002abe7f72f64a。cpp:893 #UrlStruct::runXmlRpc中的4 0x00002aaab57c26d(this=0x122d140,method=“mediacontrol.onEvent”,paramList=,result=)位于Utils.cpp:146 #5 IVRUtils::executeXmlRpc中的0x00002aaab57c526(controllerUrl=0x12e2580,methodName=Traceback(最近一次调用最后一次): #6 IvrCoreSession中的0x00002AAAB54366A::\u exec\u xmlrpc\u cmd(this=0x2AAB4827F0,paramList=…,result=0x41228cb0)位于IvrCoreSession.cpp:307 #7 IvrCoreSession中的0x00002AAAB544C95::IvrCoreSession中的fireEndCallEvent(此=0x2AAB4827F0)。cpp:504 #8 IvrCoreSession中的0x00002AAAB54752D::~IvrCoreSession(this=0x2AAB4827F0,u in_chrg=)位于IvrCoreSession.cpp:101 #AmSessionContainer中的9 0x000000000047c15d::AmSessionContainer中的clean_会话(此=0x10cbdd0)。cpp:94 #AmSessionContainer中的10 0x000000000047c898::在AmSessionContainer.cpp:132处运行(此值=0x10cbdd0) #AmThread中的11 0x000000000049266c::_在AmThread.cpp:70处开始(_t=) #/lib64/libpthread.so.0中的start_线程()中的12 0x000000397ec0673d #13/lib64/libc.so.6中克隆()中的0x000000397e0d40cd 此错误每6天出现一次。我们使用xmlrpc-c lib和curl build选项——启用线程解析程序。请告诉我们一些想法。
谢谢。

这看起来很危险:

警告:源文件i