From Fedora Project Wiki

Line 63: Line 63:
 
From the gdb shell type `set logging on'
 
From the gdb shell type `set logging on'
  
<pre>(gdb) set logging on
+
<pre>Sample ouput...
You should see..
+
(gdb) set logging on
 
Copying output to gdb.txt.
 
Copying output to gdb.txt.
 
Current language:  auto; currently minimal</pre>
 
Current language:  auto; currently minimal</pre>
Line 70: Line 70:
 
Then type cont and redo the steps in Thunderbird that caused the error your experiencing.
 
Then type cont and redo the steps in Thunderbird that caused the error your experiencing.
  
<pre>(gdb) cont
+
<pre>Sample output...
You should see..
+
(gdb) cont
 
Continuing.</pre>
 
Continuing.</pre>
  
Line 77: Line 77:
 
thread apply all bt.
 
thread apply all bt.
  
<pre>Sample output..
+
<pre>Sample output...
 
^C
 
^C
 
Program received signal SIGINT, Interrupt.
 
Program received signal SIGINT, Interrupt.
Line 94: Line 94:
 
Press return until you are returned to the gdb shell then type quit and exit the debugger.
 
Press return until you are returned to the gdb shell then type quit and exit the debugger.
  
<pre>Sample output..
+
<pre>Sample output...
 
Current language:  auto; currently minimal
 
Current language:  auto; currently minimal
 
(gdb) quit
 
(gdb) quit

Revision as of 10:43, 7 October 2009


Identifying your problem area

To be able to identify if it's Thunderbird or Thunderbird extensions you need to disable all Thunderbird extension you have installed and enabled. You do so by starting Thunderbird, go to "Tools", select "Add-ons" and disable all extensions listed there.

Quit Thunderbird and start it again. Recreate whatever you did that caused the problem your experiencing and see if it persists.

If the problem persisted go to "Debugging Thunderbird".

If the problem did not persist enable each extension and try to recreate the problem then disable the extension you just enabled again until you come across which extension is causing the problem then go to "Debugging Thunderbird Extensions".

Information to include in your report

All bug reports

In all cases, the following should be mentioned and attached to your bug report:

  • What version of Thunderbird your using.
Error creating thumbnail: File missing
You can determine which version of Thunderbird you have installed by starting Thunderbird go to "Help" and choose "About" or open up a terminal window and run:
$ rpm -q thunderbird

  • The exact command-line used if an command was used to start Thunderbird.
  • Screen shot of Thunderbird window if an graphical error occurs or Thunderbird shows an error.
  • List of Thunderbird extension you have installed.

Thunderbird Extensions problems

As well as the information from the 'All bug reports' section, include the following information:

Debugging Thunderbird

Error creating thumbnail: File missing
Always review and sanitize your logs before submitting them. Often when turning on debug logging or when using debuggers in application they will show/store sensitive information such as passwords etc. simply remove or replace the sensitive string with xxxx in the logs before submitting them.

Install Thunderbird debug package.

$ su -c 'debuginfo-install thunderbird'

Find Thunderbirds process ID ( PID )

$ ps -C thunderbird-bin

Sample output:

$ ps -C thunderbird-bin
  PID TTY          TIME CMD
  22924 ?        01:15:06 thunderbird-bin

Attache GNU Project Debugger to Thunderbirds PID

$ gdb thunderbird-bin 22924

If gdb complaints about "Missing separate debuginfos" then type "quit" in the gdb shell and do a copy paste of the debuginfo-install entry and install it the same way as above then and rerun the gdb thunbird-bin PID command.

 Sample error entry:

Missing separate debuginfos, use: debuginfo-install PackageKit-gtk-module-0.4.9-1.fc11.x86_64 audiofile-0.2.6-10.fc11.x86_64 elfutils-libelf-0.142-1.fc11.x86_64 esound-libs-0.2.41-2.fc11.x86_64 gecko-mediaplayer-0.9.8-1.fc11.x86_64 gvfs-1.2.3-12.fc11.x86_64 libXScrnSaver-1.1.3-2.fc11.x86_64 libXext-1.0.99.1-3.fc11.x86_64 libgnomeui-2.24.1-1.fc11.x86_64 libical-0.43-4.fc11.x86_64 libtool-ltdl-2.2.6-11.fc11.1.x86_64 libvorbis-1.2.0-8.fc11.x86_64 libxml2-2.7.5-1.fc11.x86_64 sqlite-3.6.12-3.fc11.x86_64 thunderbird-enigmail-0.97a-0.1.cvs20090721.fc11.x86_64

Enable logging to a file in gdb.

From the gdb shell type `set logging on'

Sample ouput... 
(gdb) set logging on
Copying output to gdb.txt.
Current language:  auto; currently minimal

Then type cont and redo the steps in Thunderbird that caused the error your experiencing.

Sample output...
(gdb) cont
Continuing.

After you have recreated the steps that causes the error your experiencing press CTRL-C in the gdb shell and type thread apply all bt.

Sample output...
^C
Program received signal SIGINT, Interrupt.
0x0000003846ad50d3 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:87
87	  int result = INLINE_SYSCALL (poll, 3, CHECK_N (fds, nfds), nfds, timeout);
Current language:  auto; currently minimal
(gdb) thread apply all bt

Thread 19 (Thread 0x7fffdacff910 (LWP 20935)):
Output trunkated.... 

---Type <return> to continue, or q <return> to quit--

Press return until you are returned to the gdb shell then type quit and exit the debugger.

Sample output...
Current language:  auto; currently minimal
(gdb) quit
The program is running.  Quit anyway (and kill it)? (y or n) y

quit and sample output

attache gdb.txt to report..

Debugging Thunderbird Extensions

  1. FIXME PRACTICE IS CALLING