Linux環境的C++可執行程式core了
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f632dee6726, pid=7816, tid=140064030222144
#
# JRE version: 6.0_35-b35
# Java VM: OpenJDK 64-Bit Server VM (23.25-b01 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea6 1.13.7
# Distribution: CentOS Linux release 7.1.1503 (Core) , package rhel-1.13.7.1.el7_1-x86_64
# Problematic frame:
# C [libc.so.6+0x7e726]
gdb進去core檔案
Program terminated with signal 6, Aborted.
#0 0x00007f632de9d5d7 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install ogTAP312RAP15Gen-20151215-1.x86_64
(gdb) bt
#0 0x00007f632de9d5d7 in raise () from /lib64/libc.so.6
#1 0x00007f63315446c6 in skgesigOSCrash () from /usr/lib/oracle/11.2/client64/lib/libclntsh.so.11.1
#2 0x00007f63317f5f79 in kpeDbgSignalHandler () from /usr/lib/oracle/11.2/client64/lib/libclntsh.so.11.1
#3 0x00007f63315448d6 in skgesig_sigactionHandler () from /usr/lib/oracle/11.2/client64/lib/libclntsh.so.11.1
#4 <signal handler called>
#5 0x00007f632de9d5d7 in raise () from /lib64/libc.so.6
#6 0x00007f632de9ecc8 in abort () from /lib64/libc.so.6
#7 0x00007f632f424819 in os::die() () from /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/jre/lib/amd64/server/libjvm.so
#8 0x00007f632f53ed83 in WatcherThread::run() () from /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/jre/lib/amd64/server/libjvm.so
#9 0x00007f632f423532 in java_start(Thread*) () from /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/jre/lib/amd64/server/libjvm.so
#10 0x00007f632dc4fdf5 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f632df5e1ad in clone () from /lib64/libc.so.6
(gdb) info threads
Id Target Id Frame
19 Thread 0x7f6320f4f700 (LWP 7832) 0x00007f632dc53ab2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
18 Thread 0x7f632225e700 (LWP 7825) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
17 Thread 0x7f632235f700 (LWP 7824) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
16 Thread 0x7f6322460700 (LWP 7823) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
15 Thread 0x7f6322864700 (LWP 7819) 0x00007f632dc53ab2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
14 Thread 0x7f6322561700 (LWP 7822) 0x00007f632dc557c0 in sem_wait () from /lib64/libpthread.so.0
13 Thread 0x7f6322662700 (LWP 7821) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
12 Thread 0x7f6320e4e700 (LWP 7833) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
11 Thread 0x7f6322763700 (LWP 7820) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
10 Thread 0x7f6328574700 (LWP 7818) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
9 Thread 0x7f6328675700 (LWP 7817) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
8 Thread 0x7f6321a9c700 (LWP 7829) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
7 Thread 0x7f6332c46740 (LWP 7816) 0x00007f632df6bb6c in __lll_lock_wait_private () from /lib64/libc.so.6
6 Thread 0x7f6320d4d700 (LWP 7834) 0x00007f632dc53ab2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
5 Thread 0x7f6321c9e700 (LWP 7827) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
4 Thread 0x7f632189a700 (LWP 7831) 0x00007f632df53b7d in poll () from /lib64/libc.so.6
3 Thread 0x7f632199b700 (LWP 7830) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
2 Thread 0x7f6321b9d700 (LWP 7828) 0x00007f632dc53705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
* 1 Thread 0x7f632215d700 (LWP 7826) 0x00007f632de9d5d7 in raise () from /lib64/libc.so.6
貌似是死鎖了，暫時沒有思路了
uj5u.com熱心網友回復：
## A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f014c7c6726, pid=22831, tid=139643636057920
#
# JRE version: 6.0_35-b35
# Java VM: OpenJDK 64-Bit Server VM (23.25-b01 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea6 1.13.7
# Distribution: CentOS Linux release 7.1.1503 (Core) , package rhel-1.13.7.1.el7_1-x86_64
# Problematic frame:
# C [libc.so.6+0x7e726]# [ timer expired, abort... ]
ORA-24550: signal received: [si_signo=6] [si_errno=0] [si_code=-6] [si_int=0] [si_ptr=(nil)] [si_addr=0x6f0000592f]
[1]+ Aborted (core dumped) ogTAP312RAP15Gen inst1
uj5u.com熱心網友回復：
1.檢查所有加鎖的地方，是否加鎖和解鎖一一匹配，錯誤回傳是否忘記解鎖。。。。2.所有函式的地方進出打日志，定位到哪個函式，然后再進一步分析。。。
uj5u.com熱心網友回復：
我是PRO*C遇到 今天剛遇到 skgesigOScrash這種 然后區域變數的地址被改了 你最終有沒有找出什么問題 ORACLE 2014年別人提問的支持回答給的是程式泄露 或者可能ORALCE新問題 。BIM的某個一大堆英語 然后說是ORACLE的BUG 。也有人分析他的插入的東西 什么么reject 然后core 。個程式有的運行半年也沒有這個錯誤 。這個4臺在運行 有一臺出現這個錯誤。我那個PRO*C使用的是單執行緒的 。但是core 0是在 libpthread 然后后面類似一樣 再出現信號句柄呼叫 ，接著才是我那個堆疊的區域變數穿到函式里 地址變了 在取指加鎖uj5u.com熱心網友回復：
我還看到一個Oracle OCI關閉core 的東西的 這種我也沒懂轉載請註明出處，本文鏈接：https://www.uj5u.com/caozuo/44482.html
標籤：應用程序開發區