C ++应用程序崩溃 [英] C++ application crash

问题描述

C ++应用程序崩溃，核心文件显示错误

C++ application gets crashed with the core file showing error

warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff79e54000
Core was generated by `./server'.
Program terminated with signal 6, Aborted.
#0 0x0000003b67230265 in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x0000003b67230265 in raise () from /lib64/libc.so.6
#1 0x0000003b67231d10 in abort () from /lib64/libc.so.6
#2 0x0000003b6726a9bb in __libc_message () from /lib64/libc.so.6
#3 0x0000003b6727247f in _int_free () from /lib64/libc.so.6
#4 0x0000003b672728db in free () from /lib64/libc.so.6
#5 0x00000000004060df in operator delete (p=0x20030190) at ../lib/m_string.cpp:43
#6 0x0000000000403892 in TStr::~TStr (this=0x2102c980, __in_chrg=<value optimized out>) at ../lib/m_string.cpp:175 – 

能够理解这个问题。以下是我已验证 https://bugzilla.redhat.com/show_bug.cgi的链接？id = 959013

could able to understand about this issue. Here is the link that i have verified https://bugzilla.redhat.com/show_bug.cgi?id=959013

显示vdso文件的大小不够。这是在路径/ proc / self / maps。

shows that the size of vdso file is not enough. which is in path /proc/self/maps.

请让我知道这是什么样的问题，请为此建议修正。

please let me know what kind of issue is this and please suggest a fix for this.

推荐答案

这是什么样的问题

what kind of issue is this

$ c> malloc 或 free 是先前堆损坏的确切迹象。

Any crash inside malloc or free is a sure sign of previous heap corruption.

使用 Valgrind 或 AddressSanitizer （也加入GCC-4.8）找出根本原因。

Use Valgrind or AddressSanitizer (incorporated into GCC-4.8 as well) to find the root cause.

忽略 vdso - 正如Tom Tromey所说，它与问题无关。

Ignore vdso -- as Tom Tromey said, it has nothing to do with the problem.

这篇关于C ++应用程序崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！