From a81257ccf5d17f9733b767c61be84820f4033321 Mon Sep 17 00:00:00 2001 From: Samuel Ortiz Date: Tue, 17 Aug 2010 17:49:01 +0200 Subject: [PATCH] Backtrace support documentation --- doc/backtrace.txt | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 doc/backtrace.txt diff --git a/doc/backtrace.txt b/doc/backtrace.txt new file mode 100644 index 0000000..951aa06 --- /dev/null +++ b/doc/backtrace.txt @@ -0,0 +1,28 @@ +ConnMan backtraces +****************** + +ConnMan dumps backtraces upon segmentation faults, bus errors and other +crashing signals. Regardless of the debug level you started connmand with, the +backtrace will be dumped to syslog. + +The ConnMan backtraces start with the following line: + ++++++++ ConnMan backtrace ++++++++ +and will try to display function names if those can be resolved from the stack +addresses. All static functions name will not appeared for example. + +For a more complete and useful stack frame output you can use the +test/backtrace script. It takes the actual binary that crashed and the +connmand logs. The logs can contain any connman debug strings on top of the +backtrace. + +Here is an example of the backtrace script usage: + +me@localhost:[~]$ backtrace /sbin/connmand connman.log +-------- ConnMan backtrace -------- +[0]: __connman_debug_list_available() [log.c:117] +[1]: connman_driver_register() [element.c:515] +[2]: __connman_driver_rescan() [element.c:490] +[3]: disable_technology() [manager.c:391] +[4]: generic_message() [object.c:262] +----------------------------------- + -- 2.7.4