Skip to content

Debugging Logs

Jump to bottom
dx edited this page Sep 14, 2016 · 13 revisions

Debugging logs can often be very useful for determining the root cause of an issue. Please note, these logs often contain sensitive data, and are likely not ideal for posting to the issue tracker, public pastebins, or anywhere else.

If a log has been requested from you, you should email it directly to the developer, dx@dxzone.com.ar, to prevent from publicly displaying the log. Please DO NOT email for general support issues, use the issue tracker instead. It keeps things organized and it means other people can help too. Also consider searching for old issues first, since your question might be answered already.

By sending a debugging log, you understand there is a risk of your sensitive information potentially being exposed. Before submitting a debugging log, it is highly recommended that you change your password, or reset your app password.

Debug Log on Windows

  1. Read the important information at the top
  2. Start pidgin, if it is not already running
  3. Disable all accounts, except the account to debug
  4. Quit pidgin completely and ensure it is not running
  5. Open Command Prompt and run the following commands:
set PURPLE_UNSAFE_DEBUG=1
set PURPLE_VERBOSE_DEBUG=1
cd "C:\Program Files\Pidgin"
pidgin.exe --debug 2>&1 > "%USERPROFILE%\pidgin.log"
echo %USERPROFILE%

Notes:

  • Program Files will be Program Files (x86) on 64-bit Windows.
  • The debug log will reside in %USERPROFILE%, which is echoed above.

Debug Log on *NIX

  1. Read the important information at the top
  2. Start pidgin, if it is not already running
  3. Disable all accounts, except the account to debug
  4. Quit pidgin completely and ensure it is not running
  5. In a terminal run the following command:
$ PURPLE_UNSAFE_DEBUG=1 PURPLE_VERBOSE_DEBUG=1 pidgin --debug &> pidgin.log

Obtaining a GDB Backtrace

$ PURPLE_UNSAFE_DEBUG=1 PURPLE_VERBOSE_DEBUG=1 gdb \
    -ex 'handle SIGPIPE nostop noprint pass' \
    -ex "set breakpoint pending on" \
    -ex "set pagination off" \
    -ex run -ex bt \
    --args pidgin --debug

Obtaining a Valgrind Report

$ PURPLE_UNSAFE_DEBUG=1 PURPLE_VERBOSE_DEBUG=1 valgrind \
    --tool=memcheck \
    --leak-check=yes \
    --leak-resolution=high \
    --num-callers=20 \
    --trace-children=no \
    --child-silent-after-fork=yes \
    --track-fds=yes \
    pidgin --debug &> pidgin-valgrind.log
Clone this wiki locally