Debugging - dino/dino GitHub Wiki
Stack trace
If Dino crashes, a stack trace can be obtained by executing Dino within gdb. Make sure you have debug symbols installed.
gdb dino
> r // Starts dino
[Do whatever makes Dino crash]
> bt // To obtain the stack trace
To get traces of runtime criticals, use gdb --args dino --g-fatal-warnings
.
Debug output
Additional output will be printed when setting the environment variable G_MESSAGES_DEBUG
. Setting it to all
will also print output from non-Dino components (Gtk, Glib, ...).
env G_MESSAGES_DEBUG=all dino
You can filter for which components debug output should be printed by replacing all
with libdino
and/or OMEMO
env G_MESSAGES_DEBUG=libdino,OMEMO dino
View XML stanzas
Starting dino
with --print-xmpp=[filter]
results in stanzas being printed to stdout. You can create complex filters to specify which stanzas should be printed.
--print-xmpp= |
Result |
---|---|
all |
All stanzas |
message |
Message stanzas |
message.body |
Message stanzas with a body child node |
message[[email protected]] |
Message stanzas with the to attribute set to [email protected] |
presence.{jabber:x:signed}:x |
Presence stanzas having a child node x with namespace jabber:x:signed |
message|iq |
Message and Iq stanzas |