Telepathy debugging: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
== Enabling debug logs for Telepathy ==
== Enabling debug logs for Telepathy ==


When there are certain kinds of problems with collaboration on the XO, it is useful to developers to have log files for debugging purposes. Here is how to enable these log files. If you haven't already seen [[Attaching Sugar Logs to Tickets]], see that page first.
When there are certain kinds of problems with collaboration on the XO, it is useful to developers to have log files for debugging purposes. Here is how to enable these log files.

'''If you haven't already seen [[Attaching Sugar Logs to Tickets]], see that page first.'''


* [http://wiki.laptop.org/go/Olpc-utils#.2Fhome.2Folpc.2F.xsession Enable your <tt>/home/olpc/.xsession</tt> file]
* [http://wiki.laptop.org/go/Olpc-utils#.2Fhome.2Folpc.2F.xsession Enable your <tt>/home/olpc/.xsession</tt> file]
cp /home/olpc/.xsession-example /home/olpc/.xsession
cp /home/olpc/.xsession-example /home/olpc/.xsession
* Edit .xsession and uncomment the lines about GABBLE_DEBUG, GABBLE_LOGFILE, SALUT_DEBUG, SALUT_LOGFILE and PRESENCESERVICE_DEBUG by removing the initial '#' character
* Edit .xsession and uncomment the lines about GABBLE_DEBUG, GABBLE_LOGFILE, SALUT_DEBUG, SALUT_LOGFILE, PRESENCESERVICE_DEBUG and '''SUGAR_LOGGER_LEVEL''' by removing the initial '#' character
* 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.
* 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
* Reboot

Revision as of 07:59, 7 October 2008

Enabling debug logs for Telepathy

When there are certain kinds of problems with collaboration on the XO, it is useful to developers to have log files for debugging purposes. Here is how to enable these log files.

If you haven't already seen Attaching Sugar Logs to Tickets, see that page first.

 cp /home/olpc/.xsession-example /home/olpc/.xsession
  • Edit .xsession and uncomment the lines about GABBLE_DEBUG, GABBLE_LOGFILE, SALUT_DEBUG, SALUT_LOGFILE, PRESENCESERVICE_DEBUG and SUGAR_LOGGER_LEVEL by removing the initial '#' character
  • 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. By default, core files are disabled on the XO. Here is how to enable them.

  • As root:
 echo /tmp/core-%p-%e > /proc/sys/kernel/core_pattern
This tells the kernel to put core files into the /tmp directory. This will only be effective until the laptop is rebooted. To make it persistent 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.

Debugging scenarios

XXX

  • no presence seen on (or of) other machines/laptops
  • activity was shared but doesn't appear on other laptops
  • invitation was sent but not received
  • other sharing problems