linux 段错误,我快疯了,搞了两天了
Core was generated by `./test'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /opt/SinoVoice/jTTS-5.0.1.0/bin/libjTTS_ML.so...done.
Loaded symbols for /opt/SinoVoice/jTTS-5.0.1.0/bin/libjTTS_ML.so
Reading symbols from /opt/SinoVoice/jTTS-5.0.1.0/bin/libjTTS_Audio.so...done.
Loaded symbols for /opt/SinoVoice/jTTS-5.0.1.0/bin/libjTTS_Audio.so
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/tls/libpthread.so.0...done.
Loaded symbols for /lib/tls/libpthread.so.0
Reading symbols from /usr/lib/libstdc++.so.6...done.
Loaded symbols for /usr/lib/libstdc++.so.6
Reading symbols from /lib/tls/libm.so.6...done.
Loaded symbols for /lib/tls/libm.so.6
Reading symbols from /lib/tls/libc.so.6...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0 0x00c89f68 in ?? ()
(gdb) bt
#0 0x00c89f68 in ?? ()
#1 0x001f3597 in exit () from /lib/tls/libc.so.6
#2 0x001ddded in __libc_start_main () from /lib/tls/libc.so.6
#3 0x08048a05 in _start ()
(gdb)
程序大概是这样的
test调用a.so,然后a.so中调用b.so。
程序出现段错误以后,就是上面的内容。谁知道这什么问题啊。我快疯了。!!!!!!!
Program terminated with signal 11, Segmentation fault.
Reading symbols from /opt/SinoVoice/jTTS-5.0.1.0/bin/libjTTS_ML.so...done.
Loaded symbols for /opt/SinoVoice/jTTS-5.0.1.0/bin/libjTTS_ML.so
Reading symbols from /opt/SinoVoice/jTTS-5.0.1.0/bin/libjTTS_Audio.so...done.
Loaded symbols for /opt/SinoVoice/jTTS-5.0.1.0/bin/libjTTS_Audio.so
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/tls/libpthread.so.0...done.
Loaded symbols for /lib/tls/libpthread.so.0
Reading symbols from /usr/lib/libstdc++.so.6...done.
Loaded symbols for /usr/lib/libstdc++.so.6
Reading symbols from /lib/tls/libm.so.6...done.
Loaded symbols for /lib/tls/libm.so.6
Reading symbols from /lib/tls/libc.so.6...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0 0x00c89f68 in ?? ()
(gdb) bt
#0 0x00c89f68 in ?? ()
#1 0x001f3597 in exit () from /lib/tls/libc.so.6
#2 0x001ddded in __libc_start_main () from /lib/tls/libc.so.6
#3 0x08048a05 in _start ()
(gdb)
程序大概是这样的
test调用a.so,然后a.so中调用b.so。
程序出现段错误以后,就是上面的内容。谁知道这什么问题啊。我快疯了。!!!!!!!
...全文
相关推荐
Linux下的段错误产生的原因及调试方法
### Linux下的段错误产生的原因及调试方法在深入探讨Linux下段错误的产生原因与调试方法之前,我们先来理解一下“段错误”(Segmentation Fault)的基本概念。
段错误(linux)
### 段错误(Linux)#### 知识点解析**段错误**是程序在运行过程中发生的一种常见异常,通常表现为程序突然崩溃并提示“Segmentation fault”或简称为“Segfault”。
Linux下发生段错误时如何产生core文件
在Linux操作系统中,当一个进程由于各种原因,如非法内存访问、除以零等,触发了段错误(Segmentation Fault)时,系统可以生成一种名为core dump的文件,记录程序崩溃时的内存状态和调用堆栈信息
Linux C段错误定位
本文将探讨如何在Linux环境下,通过信号处理和调试技巧来定位C段错误。首先,我们需要理解什么是SIGSEGV信号。
Linux下的段错误Segmentationfault产生的原因及调试方法经典.pdf
"Linux下的段错误Segmentationfault产生的原因及调试方法经典"在 Linux 系统中,段错误(Segmentation fault)是一种常见的错误,它是指访问了错误的内存段,或者访问了没有权限的内存区域


