Linux 进程由信号 6 终止,核心在 libc 中显示一种循环

声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow 原文地址: http://stackoverflow.com/questions/3989802/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示:将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间:2020-08-04 23:45:27  来源:igfitidea点击:

Process terminated by signal 6, core shows kind of loop in libc

linuxgdbcoreglibcsigabrt

提问by Vikash

On analysis of the core of a process (terminated by signal 6), on LINUX, stack bt shows :

分析一个进程的核心(由信号 6 终止),在 LINUX 上,堆栈 bt 显示:

Core was generated by `/opt/namsam/pac_rrc_qx_e1/bin/rrcprb'.

Program terminated with signal 6, Aborted.

#0  0x0000005555ffb004 in epoll_wait () from /lib64/libc.so.6

(gdb) bt

#0  0x0000005555ffb004 in epoll_wait () from /lib64/libc.so.6
#1  0x0000005555ffafe8 in __epoll_wait_nocancel () from /lib64/libc.so.6
#2  0x0000005555ffafe8 in __epoll_wait_nocancel () from /lib64/libc.so.6
#3  0x0000005555ffafe8 in __epoll_wait_nocancel () from /lib64/libc.so.6
#4  0x0000005555ffafe8 in __epoll_wait_nocancel () from /lib64/libc.so.6
#5  0x0000005555ffafe8 in __epoll_wait_nocancel () from /lib64/libc.so.6
#6  0x0000005555ffafe8 in __epoll_wait_nocancel () from /lib64/libc.so.6
#7  0x0000005555ffafe8 in __epoll_wait_nocancel () from /lib64/libc.so.6

libc seems to have gone in some loop.. Did something go wrong with the application "rrcprb" here..? please help me debug this issue..?

libc 似乎进入了某个循环.. 这里的应用程序“rrcprb”有问题吗..?请帮我调试这个问题..?

回答by Employed Russian

Since __epoll_wait_nocanceldoes not call itself, it's pretty clear that the stack trace you've got is bogus. Most likely cause is incorrect unwind descriptors in your libc.so.6.

由于__epoll_wait_nocancel不调用自身,很明显您获得的堆栈跟踪是伪造的。最可能的原因是libc.so.6.

It's also somewhat unlikely that you actually crashed in epoll_wait. Try thread apply all where, and see if there is a "more interesting" stack trace / thread for you to look at.

您实际上也不太可能坠入epoll_wait. 试试看thread apply all where,看看是否有“更有趣”的堆栈跟踪/线程供您查看。