diff options
| author | Sebastien Helleu <flashcode@flashtux.org> | 2012-02-24 13:51:29 +0100 |
|---|---|---|
| committer | Sebastien Helleu <flashcode@flashtux.org> | 2012-02-24 13:51:29 +0100 |
| commit | b0ef8fc6e350fb877ff53c9ccaae7cbd2edb07d5 (patch) | |
| tree | c3f22c7c8ba5a269a314a2658cd5c3b5a7c13b2c | |
| parent | 0be9ae30174d10808b102aa7b9de46f0c552ee81 (diff) | |
| download | weechat-b0ef8fc6e350fb877ff53c9ccaae7cbd2edb07d5.zip | |
doc: add gdb commands to log output in a file (user guide)
| -rw-r--r-- | doc/de/weechat_user.de.txt | 3 | ||||
| -rw-r--r-- | doc/en/weechat_user.en.txt | 3 | ||||
| -rw-r--r-- | doc/fr/weechat_user.fr.txt | 3 | ||||
| -rw-r--r-- | doc/it/weechat_user.it.txt | 3 |
4 files changed, 12 insertions, 0 deletions
diff --git a/doc/de/weechat_user.de.txt b/doc/de/weechat_user.de.txt index a32ecfb62..03cc994d2 100644 --- a/doc/de/weechat_user.de.txt +++ b/doc/de/weechat_user.de.txt @@ -246,6 +246,9 @@ Nun startet man 'gdb' und führt den Befehl `bt full` innerhalb gdb aus um die F auszugeben. Eine Fehlermeldung von gdb sieht z.B. wie folgt aus: ---------------------------------------- +(gdb) set logging file /tmp/crash.txt +(gdb) set logging on +Copying output to /tmp/crash.txt. (gdb) bt full #0 0x00007f9dfb04a465 in raise () from /lib/libc.so.6 #1 0x00007f9dfb04b8e6 in abort () from /lib/libc.so.6 diff --git a/doc/en/weechat_user.en.txt b/doc/en/weechat_user.en.txt index d86bb22b1..6bc113f15 100644 --- a/doc/en/weechat_user.en.txt +++ b/doc/en/weechat_user.en.txt @@ -247,6 +247,9 @@ Then under gdb, use command `bt full` to display backtrace. You will see something like that: ---------------------------------------- +(gdb) set logging file /tmp/crash.txt +(gdb) set logging on +Copying output to /tmp/crash.txt. (gdb) bt full #0 0x00007f9dfb04a465 in raise () from /lib/libc.so.6 #1 0x00007f9dfb04b8e6 in abort () from /lib/libc.so.6 diff --git a/doc/fr/weechat_user.fr.txt b/doc/fr/weechat_user.fr.txt index 5029dcc08..6d44f0e83 100644 --- a/doc/fr/weechat_user.fr.txt +++ b/doc/fr/weechat_user.fr.txt @@ -254,6 +254,9 @@ Puis sous gdb, utilisez la commande `bt full` pour afficher la trace. Vous verrez quelque chose comme ceci : ---------------------------------------- +(gdb) set logging file /tmp/crash.txt +(gdb) set logging on +Copying output to /tmp/crash.txt. (gdb) bt full #0 0x00007f9dfb04a465 in raise () from /lib/libc.so.6 #1 0x00007f9dfb04b8e6 in abort () from /lib/libc.so.6 diff --git a/doc/it/weechat_user.it.txt b/doc/it/weechat_user.it.txt index ea9df5848..ae52d2f6f 100644 --- a/doc/it/weechat_user.it.txt +++ b/doc/it/weechat_user.it.txt @@ -255,6 +255,9 @@ All'interno di gdb, usare il comando `bt full` per visualizzare il backtrace. Verrà mostrato qualcosa di simile a questo: ---------------------------------------- +(gdb) set logging file /tmp/crash.txt +(gdb) set logging on +Copying output to /tmp/crash.txt. (gdb) bt full #0 0x00007f9dfb04a465 in raise () from /lib/libc.so.6 #1 0x00007f9dfb04b8e6 in abort () from /lib/libc.so.6 |