Thread 1 “SLRobot” received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at …/sysdeps/unix/sysv/linux/raise.c:51
51 …/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at …/sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007ffff3a2f801 in __GI_abort () at abort.c:79
#2 0x00007ffff3a78897 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff3ba5b9a “%s\n”) at …/sysdeps/posix/libc_fatal.c:181
#3 0x00007ffff3a7f90a in malloc_printerr (str=str@entry=0x7ffff3ba3cba “corrupted double-linked list”) at malloc.c:5350
#4 0x00007ffff3a840a9 in _int_malloc (av=av@entry=0x7ffff3ddac40 <main_arena>, bytes=bytes@entry=96) at malloc.c:3926
#5 0x00007ffff3a862ed in __GI___libc_malloc (bytes=96) at malloc.c:3065
#6 0x00007ffff408b298 in operator new(unsigned long) () from /usr/li
C++ new abort
最新推荐文章于 2024-05-23 15:04:43 发布
博客内容讲述了在C++中遇到的`new`操作引发SIGABRT异常的问题,通过堆栈跟踪和内存检查工具valgrind发现了由于不同库中存在同名但结构体大小不一致的符号导致的内存越界问题。解决此类问题的关键在于避免同名符号冲突并确保正确链接。
摘要由CSDN通过智能技术生成