summaryrefslogtreecommitdiff
path: root/Debugging.mdwn
diff options
context:
space:
mode:
authorsmcv <smcv@web>2013-06-26 04:01:32 -0700
committertelepathy <iki-telepathy@freedesktop.org>2013-06-26 04:01:32 -0700
commit554505a268b820f858c0c7a7bda19635e4359799 (patch)
tree48cd517dd91d9b1cb73c0f6b0f56d5dbe2fff152 /Debugging.mdwn
parent62086f10851bb528b72f640a523a1ab21dd1d39d (diff)
fix preformatted text
Diffstat (limited to 'Debugging.mdwn')
-rw-r--r--Debugging.mdwn34
1 files changed, 14 insertions, 20 deletions
diff --git a/Debugging.mdwn b/Debugging.mdwn
index 2925d5e..f50d02e 100644
--- a/Debugging.mdwn
+++ b/Debugging.mdwn
@@ -1,5 +1,3 @@
-
-
## If you are using Empathy...
Empathy has a debug console which shows you the debug output from components of your choice. See [[the Empathy wiki|http://live.gnome.org/Empathy/Debugging]] for more details.
@@ -21,10 +19,8 @@ Connection manager executables don't generally live in your `$PATH`, so you'll n
First, quit your IM client (such as Empathy), and wait a few seconds for the connection managers to quit of their own accord. Then, in a terminal, run:
+ G_MESSAGES_DEBUG=all FOO_PERSIST=1 FOO_DEBUG=all /path/to/telepathy-foo 2>&1 | tee foo.log
-[[!format txt """
-G_MESSAGES_DEBUG=all FOO_PERSIST=1 FOO_DEBUG=all /path/to/telepathy-foo 2>&1 | tee foo.log
-"""]]
(where `foo` should be `gabble` for Jabber, and the name of the relevant CM for the protocol you're having trouble with, as listed on [[Components|Components]]). Now, start your IM client again, and reproduce the problem; debugging output should appear in your terminal, and be written to `foo.log`. (You can set the `_DEBUG` variable to values other than `all` if you only want the debugging output from a certain part of the CM, but usually this is unnecessary.)
If the connection manager complains about "name already or use" and quits immediately, you should `kill` any existing instances of it and try again.
@@ -70,21 +66,19 @@ On Debian-like systems, debugging packages include:
You might be able to obtain debug information using gdb (for connection managers, you probably also want to use the X_PERSIST variable for this):
+ $ GABBLE_PERSIST=1 gdb telepathy-gabble
+ GNU gdb 6.7.1-debian
+ Copyright (C) 2007 Free Software Foundation, Inc.
+ License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+ This is free software: you are free to change and redistribute it.
+ There is NO WARRANTY, to the extent permitted by law. Type "show copying"
+ and "show warranty" for details.
+ This GDB was configured as "i486-linux-gnu"...
+ Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
+ (gdb) r
+ Starting program: /usr/bin/telepathy-gabble
+ ** (telepathy-gabble:17666): DEBUG: started version 0.6.0 (telepathy-glib version 0.7.0)
-[[!format txt """
-$ GABBLE_PERSIST=1 gdb telepathy-gabble
-GNU gdb 6.7.1-debian
-Copyright (C) 2007 Free Software Foundation, Inc.
-License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
-This is free software: you are free to change and redistribute it.
-There is NO WARRANTY, to the extent permitted by law. Type "show copying"
-and "show warranty" for details.
-This GDB was configured as "i486-linux-gnu"...
-Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
-(gdb) r
-Starting program: /usr/bin/telepathy-gabble
-** (telepathy-gabble:17666): DEBUG: started version 0.6.0 (telepathy-glib version 0.7.0)
-"""]]
If the program crashes while running under gdb, use the "bt" command to obtain a backtrace.
If you can't make it crash while running under gdb (this is not an uncommon state of affairs, for reasons I won't go into here):
@@ -113,4 +107,4 @@ Electric Fence can find some memory allocation bugs.
To use it, run Programs with LD_PRELOAD=/usr/lib/libefence.so.0.0.
-* [[Electric Fence home page|http://perens.com/FreeSoftware/]]. \ No newline at end of file
+* [[Electric Fence home page|http://perens.com/FreeSoftware/]].