C++代码core

悠然现南山 2016-07-07 11:21:27
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
貌似是死锁了,暂时没有思路了
...全文
355 4 打赏 收藏 转发到动态 举报
写回复
用AI写文章
4 条回复
切换为时间正序
请发表友善的回复…
发表回复
Datrilla 2020-03-13
  • 打赏
  • 举报
回复
我还看到一个Oracle OCI关闭core 的东西的 这种我也没懂
Datrilla 2020-03-13
  • 打赏
  • 举报
回复
我是PRO*C遇到 今天刚遇到 skgesigOScrash这种 然后局部变量的地址被改了 你最终有没有找出什么问题 ORACLE 2014年别人提问的支持回答给的是程序泄露 或者可能ORALCE新问题 。BIM的某个一大堆英语 然后说是ORACLE的BUG 。也有人分析他的插入的东西 什么么reject 然后core 。个程序有的运行半年也没有这个错误 。这个4台在运行 有一台出现这个错误。我那个PRO*C使用的是单线程的 。但是core 0是在 libpthread 然后后面类似一样 再出现信号句柄调用 ,接着才是我那个堆栈的局部变量穿到函数里 地址变了 在取指加锁
ec06cumt 2016-07-08
  • 打赏
  • 举报
回复
1.检查所有加锁的地方,是否加锁和解锁一一匹配,错误返回是否忘记解锁。。。。 2.所有函数的地方进出打日志,定位到哪个函数,然后再进一步分析。。。
悠然现南山 2016-07-07
  • 打赏
  • 举报
回复
# # 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

23,114

社区成员

发帖
与我相关
我的任务
社区描述
Linux/Unix社区 应用程序开发区
社区管理员
  • 应用程序开发区社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧