diff options
| author | jpeeler <jpeeler@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-06-11 16:11:09 +0000 |
|---|---|---|
| committer | jpeeler <jpeeler@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-06-11 16:11:09 +0000 |
| commit | 178171468aa29b67846684a743c388015193141c (patch) | |
| tree | 89e9dd3ed9a835feea03666c4c2456c57647bfe1 /doc | |
| parent | 97c50a79c38f41d05197f2e90336efcf5f6b437d (diff) | |
add instructions for logging gdb output via set logging on
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@121804 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/backtrace.txt | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/backtrace.txt b/doc/backtrace.txt index d4e13c863..ce39b0a3e 100644 --- a/doc/backtrace.txt +++ b/doc/backtrace.txt @@ -76,6 +76,11 @@ Loaded symbols for /usr/lib/asterisk/modules/app_externalivr.so #0 0x29b45d7e in ?? () (gdb) +In order to make extracting the gdb output easier, you may wish to +turn on logging using "set logging on". This command will save all +output to the default file of gdb.txt, which in the end can be +uploaded as an attachment to the bug tracker. + Now at the gdb prompt, type: bt You would see output similar to: (gdb) bt @@ -178,8 +183,9 @@ Thread 1 (process 26252): That output tells us crucial information about each thread. -Now, just create an output.txt file and dump your "bt full" -(and/or "bt") ALONG WITH "thread apply all bt" into it. +Now, if you turned on logging upload your gdb.txt file. Otherwise, +create an output.txt file and dump your "bt full" (and/or "bt") +ALONG WITH "thread apply all bt" into it. Note: Please ATTACH your output, DO NOT paste it as a note. |