-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
# Crash Error #1657
Comments
You need to provide the backtrace of the dispatcher thread. |
removed |
That is not what I asked for. |
Sorry man, I dont understand. You could give a short explanation please? |
You need to switch to the dispatcher thread and print the backtrace in gdb, it doesn't even necessarily have to be the dispatcher thread, so you should just switch to all threads and post the backtrace. You switch thread with the command thread. Example:
|
Humm ok, I need to wait this crash again right? To do this commands, because I restarted the server. Waiting here for crash again PS. I was updated the Boost system |
If you didn't generate a core dump, yes, you'll have to wait for it to crash again. Please open a new issue when you have a backtrace that shows where it crashed. It would also help to build with debug flags if you're not already doing so. Use this command to generate debug build files with CMake:
|
I had already done it (compiled with debug mode), waiting crashing again, thank you for your answers . |
#0 0x0000713443ed8b13 in epoll_wait ()
#1 0x0000000000a068b4 in boost::asio::detail::epoll_reactor::run (
#2 0x0000000000a075cd in boost::asio::detail::task_io_service::do_run_one (
#3 0x0000000000a07391 in boost::asio::detail::task_io_service::run (
#4 0x0000000000a078bd in boost::asio::io_service::run (this=0x7c6f1f7711d0)
#5 0x0000000000a04e07 in ServiceManager::run (this=0x7c6f1f7711a0)
#6 0x000000000097e87d in main (argc=1, argv=0x7c6f1f7713f8)
The text was updated successfully, but these errors were encountered: