您实际上也不太可能在 epoll_wait 中崩溃。尝试thread apply all where，看看是否有“更有趣”的堆栈跟踪/线程供您查看。
Since __epoll_wait_nocancel does 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.
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.
发布评论
评论（1）
由于 __epoll_wait_nocancel 不会调用自身，因此很明显您获得的堆栈跟踪是伪造的。最可能的原因是
libc.so.6中的展开描述符不正确。您实际上也不太可能在
epoll_wait中崩溃。尝试thread apply all where，看看是否有“更有趣”的堆栈跟踪/线程供您查看。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 yourlibc.so.6.It's also somewhat unlikely that you actually crashed in
epoll_wait. Trythread apply all where, and see if there is a "more interesting" stack trace / thread for you to look at.