summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSamuel Ortiz <sameo@linux.intel.com>2010-12-15 15:16:36 +0100
committerSamuel Ortiz <sameo@linux.intel.com>2010-12-15 15:16:36 +0100
commitb8cf7c3428e1d733a41fd2d97dd2add01163254c (patch)
treebd3e6b31702996ff6ceca4e01127d308ef23f604 /doc
parenta759ad2215ddeb86179eecb7b6df7516ca520237 (diff)
downloadconnman-b8cf7c3428e1d733a41fd2d97dd2add01163254c.tar.gz
connman-b8cf7c3428e1d733a41fd2d97dd2add01163254c.tar.bz2
connman-b8cf7c3428e1d733a41fd2d97dd2add01163254c.zip
doc: Fix the backtrace document
Diffstat (limited to 'doc')
-rw-r--r--doc/backtrace.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/backtrace.txt b/doc/backtrace.txt
index fdeee090..ac8472cc 100644
--- a/doc/backtrace.txt
+++ b/doc/backtrace.txt
@@ -6,7 +6,7 @@ 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 ++++++++
+ -------- backtrace --------
and will try to display function names if those can be resolved from the stack
addresses. All static functions name will not appear for example.
@@ -18,7 +18,7 @@ backtrace.
Here is an example of the backtrace script usage:
me@localhost:[~]$ backtrace /sbin/connmand connman.log
--------- ConnMan backtrace --------
+-------- backtrace --------
[0]: __connman_debug_list_available() [log.c:117]
[1]: connman_driver_register() [element.c:515]
[2]: __connman_driver_rescan() [element.c:490]