c++ - 回溯结果没有揭示崩溃位置

Question

我正在尝试使用 backtrace 和 backtrace_symbols 结果打印出捕获 SIGSEGV 信号后代码崩溃的位置。我明确地从工作线程触发了它。我用选项 -rdynamic 编译了我的静态链接多线程 c++ 程序，我期望 backtrace_symbols 会返回一个堆栈跟踪来告诉我崩溃发生的位置，但下面的结果不是我所期望的，MyApplicationService 不是一个方法，但只是可执行文件名称，我不明白为什么。

    2013-03-07 15:13:18.119986598 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZNK5boost4_mfi3mf2IvN18my_app__service_lib14service_runnerERKNS_6system10error_codeEiEclEPS3_S7_i+0x74) [0xcd69fa]
    2013-03-07 15:13:18.119988126 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN5boost3_bi5list3INS0_5valueIPN18my_app__service_lib14service_runnerEEENS_3argILi1EEENS7_ILi2EEEEclINS_4_mfi3mf2IvS4_RKNS_6system10error_codeEiEENS0_5list2ISH_RKiEEEEvNS0_4typeIvEERT_RT0_i+0x7c) [0xcd6848]
    2013-03-07 15:13:18.119989192 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN5boost3_bi6bind_tIvNS_4_mfi3mf2IvN18my_app__service_lib14service_runnerERKNS_6system10error_codeEiEENS0_5list3INS0_5valueIPS5_EENS_3argILi1EEENSF_ILi2EEEEEEclIS7_iEEvRKT_RKT0_+0x4c) [0xcd6690]
    2013-03-07 15:13:18.119990120 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN5boost4asio6detail7binder2INS_3_bi6bind_tIvNS_4_mfi3mf2IvN18my_app__service_lib14service_runnerERKNS_6system10error_codeEiEENS3_5list3INS3_5valueIPS8_EENS_3argILi1EEENSI_ILi2EEEEEEESA_iEclEv+0x2b) [0xcd6597]
    2013-03-07 15:13:18.119991031 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN5boost4asio19asio_handler_invokeINS0_6detail7binder2INS_3_bi6bind_tIvNS_4_mfi3mf2IvN18my_app__service_lib14service_runnerERKNS_6system10error_codeEiEENS4_5list3INS4_5valueIPS9_EENS_3argILi1EEENSJ_ILi2EEEEEEESB_iEEEEvT_z+0x62) [0xcd64b0]
    2013-03-07 15:13:18.119992105 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN33boost_asio_handler_invoke_helpers6invokeIN5boost4asio6detail7binder2INS1_3_bi6bind_tIvNS1_4_mfi3mf2IvN18my_app__service_lib14service_runnerERKNS1_6system10error_codeEiEENS5_5list3INS5_5valueIPSA_EENS1_3argILi1EEENSK_ILi2EEEEEEESC_iEESO_EEvRT_RT0_+0x64) [0xcd636c]
    2013-03-07 15:13:18.119993000 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN5boost4asio6detail14signal_handlerINS_3_bi6bind_tIvNS_4_mfi3mf2IvN18my_app__service_lib14service_runnerERKNS_6system10error_codeEiEENS3_5list3INS3_5valueIPS8_EENS_3argILi1EEENSI_ILi2EEEEEEEE11do_completeEPNS1_15task_io_serviceEPNS1_25task_io_service_operationESC_m+0xb9) [0xcd605d]
    2013-03-07 15:13:18.119993884 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN5boost4asio6detail25task_io_service_operation8completeERNS1_15task_io_serviceERKNS_6system10error_codeEm+0x32) [0xccceac]
    2013-03-07 15:13:18.119994819 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN5boost4asio6detail15task_io_service10do_run_oneERNS1_11scoped_lockINS1_11posix_mutexEEERNS2_11thread_infoERKNS_6system10error_codeE+0x1a1) [0xccf4a5]
    2013-03-07 15:13:18.119995795 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN5boost4asio6detail15task_io_service3runERNS_6system10error_codeE+0x137) [0xcceffd]
    2013-03-07 15:13:18.119996845 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN5boost4asio10io_service3runEv+0x2f) [0xccf823]
    2013-03-07 15:13:18.119997845 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(_ZN18my_app__service_lib14service_runner3runEv+0x97) [0xccbb65]
    2013-03-07 15:13:18.119998914 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService(main+0x4cc) [0xcc4608]
    2013-03-07 15:13:18.119999767 [7f2279bbe720] INFO  service_runner - /lib64/libc.so.6(__libc_start_main+0xfd) [0x3f0f01ecdd]
    2013-03-07 15:13:18.120000694 [7f2279bbe720] INFO  service_runner - ../Debug/MyApplicationService() [0xcc4059]

这是我用来打印上述结果的代码:

          void *trace[16];
          char **messages = (char **)NULL;
          int i, trace_size = 0;
          SERVICE_LOG_INFO << "Receive signal " << sig ;    
          trace_size = backtrace(trace, 16);
          messages = backtrace_symbols(trace, trace_size);
          LOG << "[bt] Execution path:" ;
          for (i=1; i<trace_size; ++i)
              LOG << messages[i];

附加信息:

    OS: RHEL 6.3
    compiler: gcc 4.4.6
    compile option: -I/opt/rh/devtoolset-1.0/root/usr/include -I/opt/rh/devtoolset-1.0/root/usr/include/c++/4.7.0 -I/opt/rh/devtoolset-1.0/root/usr/include/c++/4.7.0/backward -I/opt/rh/devtoolset-1.0/root/usr/include/c++/4.7.0/x86_64-redhat-linux -I/opt/rh/devtoolset-1.0/root/usr/lib/gcc/x86_64-redhat-linux/4.7.0/include -I/opt/boost_1_52_0 -I/opt/tbb41_20121003oss/include -I/opt/libev-4.11/include -I"Myapp/include" -O0 -g3 -rdynamic -Wall -c -fmessage-length=0 -std=c++11 -fno-strict-aliasing -MMD -MP -MF"src/service_runner.d" -MT"src/service_runner.d" -o "src/service_runner.o" "../src/service_runner.cpp"

Answer 1

编译选项显示-c，所以-rdynamic被传递到编译步骤。您需要确保在链接 代码时使用它。检查是否是这种情况。

编辑:Bryan，您现在将错位的符号添加到问题中，所以您现在想问一个不同的问题。请不要那样做。

但既然你这样做了:你需要解析 backtrace_symbols 中的每一行以提取 mangled 符号并调用 __cxa_demangle在上面。策略是从字符串末尾搜索 +，然后搜索左括号 (，再次从 + 向后搜索。向后搜索的原因是，前面的文件名也可能包含这些字符(不太可能，但可能)。如果您尝试实现它并遇到问题，请打开一个新问题.