Telepathy debugging

From OLPC
Revision as of 07:20, 11 March 2008 by Morgs (talk | contribs)
Jump to navigation Jump to search

Enabling debug logs for Telepathy

Enabling .xsession

This page explains how to enable Telepathy debug output on your XO. If you haven't already seen Attaching Sugar Logs to Tickets, see that page first.

  • First you need to enable your /home/olpc/.xsession file
 cp /home/olpc/.xsession-example /home/olpc/.xsession
  • Then edit .xsession and uncomment the lines about GABBLE_DEBUG, GABBLE_LOGFILE, SALUT_DEBUG and SALUT_LOGFILE
  • For debugging lower level problems in the Telepathy connection managers, enable LM_DEBUG (for telepathy-gabble) or GIBBER_DEBUG (for telepathy-salut). Note that these will produce much bigger log files.
  • reboot

Telepathy log files are now available at /home/olpc/.sugar/default/logs/telepathy-gabble.log and /home/olpc/.sugar/default/logs/telepathy-salut.log . Be sure to attach these files if you submit a ticket about a Telepathy issue.

Capturing core files

Core files are produced when a program crashes and contain useful debugging information.

As root:

 echo /tmp/core-%p-%e > /proc/sys/kernel/core_pattern

This tells the kernel to put core files into the /tmp directory.

To make this persist across reboots, add the following line to /etc/sysctl.conf:

 kernel.core_pattern = /tmp/core-%p-%e

Add the following line to /home/olpc/.xsession:

 ulimit -c unlimited

This turns off any limit on core file size.