Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

*** Bug 442082 has been marked as a duplicate of this bug. ***

*** Bug 447086 has been marked as a duplicate of this bug. ***

*** Bug 445166 has been marked as a duplicate of this bug. ***

*** Bug 448346 has been marked as a duplicate of this bug. ***

*** Bug 449392 has been marked as a duplicate of this bug. ***

*** Bug 452480 has been marked as a duplicate of this bug. ***

*** Bug 452599 has been marked as a duplicate of this bug. ***

*** Bug 452261 has been marked as a duplicate of this bug. ***

*** Bug 453223 has been marked as a duplicate of this bug. ***

*** Bug 445049 has been marked as a duplicate of this bug. ***

*** Bug 453368 has been marked as a duplicate of this bug. ***

Can someone please remove me from receiving all the spam from this report?

*** Bug 453409 has been marked as a duplicate of this bug. ***

*** Bug 454623 has been marked as a duplicate of this bug. ***

*** Bug 462642 has been marked as a duplicate of this bug. ***

*** Bug 455077 has been marked as a duplicate of this bug. ***

*** Bug 457418 has been marked as a duplicate of this bug. ***

*** Bug 458341 has been marked as a duplicate of this bug. ***

*** Bug 462454 has been marked as a duplicate of this bug. ***

*** Bug 468904 has been marked as a duplicate of this bug. ***

*** Bug 469086 has been marked as a duplicate of this bug. ***

*** Bug 465838 has been marked as a duplicate of this bug. ***

*** Bug 470566 has been marked as a duplicate of this bug. ***

*** Bug 475312 has been marked as a duplicate of this bug. ***

*** Bug 464356 has been marked as a duplicate of this bug. ***

*** Bug 466410 has been marked as a duplicate of this bug. ***

*** Bug 466686 has been marked as a duplicate of this bug. ***

*** Bug 467236 has been marked as a duplicate of this bug. ***

*** Bug 468718 has been marked as a duplicate of this bug. ***

*** Bug 478216 has been marked as a duplicate of this bug. ***

*** Bug 479190 has been marked as a duplicate of this bug. ***

*** Bug 471048 has been marked as a duplicate of this bug. ***

*** Bug 473302 has been marked as a duplicate of this bug. ***

*** Bug 478442 has been marked as a duplicate of this bug. ***

*** Bug 476072 has been marked as a duplicate of this bug. ***

*** Bug 474803 has been marked as a duplicate of this bug. ***

*** Bug 479909 has been marked as a duplicate of this bug. ***

*** Bug 482209 has been marked as a duplicate of this bug. ***

*** Bug 466472 has been marked as a duplicate of this bug. ***

*** Bug 482396 has been marked as a duplicate of this bug. ***

(In reply to comment #1)
> Thanks for taking the time to report this bug.
> Unfortunately, that stack trace is missing some elements that will help a lot
> to solve the problem, so it will be hard for the developers to fix that crash.
> Can you get us a stack trace with debugging symbols? Please see
> http://live.gnome.org/GettingTraces for more information on how to do so.
> Thanks in advance!
> 

Just to be sure, I need to get the development packages installed correct? 

Hi Tim.

Thanks for your reply :)

Yes, we need debug symbols in order to see where and why the crash happens. Please ask your distribution for packages with debug symbols. We'd like you to install debug symbols for evolution, evolution-data-server, gtkhtml, glib, glibc and pango.

After you have installed them and bugbuddy pops up, attach the stacktrace here (not posting as a message, make searching for bugs hard...). Thanks in advance :)

Created attachment 96607 [details]
latest bug buddy report 

Not sure if this is any more usable than the last one but here you go.

*** Bug 483512 has been marked as a duplicate of this bug. ***

(In reply to comment #44)
> Not sure if this is any more usable than the last one but here you go. 
> 
I'm sorry. This stacktrace is actually useless :( I think it's not even the crasher we are discussing here. Anyway, it doesn't contain debug symbols :( Did you install packages with debug symbols?

*** Bug 483950 has been marked as a duplicate of this bug. ***

(In reply to comment #46)
> (In reply to comment #44)
> > Not sure if this is any more usable than the last one but here you go. 
> > 
> I'm sorry. This stacktrace is actually useless :( I think it's not even the
> crasher we are discussing here. Anyway, it doesn't contain debug symbols :( Did
> you install packages with debug symbols?
> 

I did install the debug packages, there have been several updates to the system since then. I'll double check that I have all the debug packages and try again. 
Just to let you know I haven't received the exact error message since I updated my system. The error occurred after doing a install of Fedora 7, maybe they forgot a dependent package?   

Created attachment 96908 [details]
Latest bug report 10/08/07

Newest error report after launching evolution from CLI with the --debug flag set.

(In reply to comment #49)
> Created an attachment (id=96908) [edit]
> Latest bug report 10/08/07
> 
Again, this is not the crasher we are dealing with in this bugreport. But now you seem to have debug symbols installed :) Plus: Thanks for that stacktrace, it seems, you just contributed to bug 457137 :)

As I think this issue is strongly related to bugs like bug 426227, bug 426807 or bug 433922 and I've seen a few people reporting that this occurs while (or after) playing around in the settings dialog, I'd like you to do this and see whether it crashes.
Good Luck!

*** Bug 484999 has been marked as a duplicate of this bug. ***

*** Bug 483946 has been marked as a duplicate of this bug. ***

*** Bug 484884 has been marked as a duplicate of this bug. ***

*** Bug 476259 has been marked as a duplicate of this bug. ***

*** Bug 486771 has been marked as a duplicate of this bug. ***

*** Bug 486535 has been marked as a duplicate of this bug. ***

*** Bug 486186 has been marked as a duplicate of this bug. ***

Created attachment 97293 [details]
bugbuddy report 10/16/2007 

Let's see if this one is the stack trace  you are hoping for, not sure why this one happened I had evolution running in the background and was playing a game.

Thanks Tim, but this is another crasher. I've seen this before, but could only find bug 487253.

*** Bug 485805 has been marked as a duplicate of this bug. ***

*** Bug 487479 has been marked as a duplicate of this bug. ***

*** Bug 488911 has been marked as a duplicate of this bug. ***

*** Bug 488487 has been marked as a duplicate of this bug. ***

*** Bug 485385 has been marked as a duplicate of this bug. ***

*** Bug 485248 has been marked as a duplicate of this bug. ***

*** Bug 489507 has been marked as a duplicate of this bug. ***

*** Bug 490032 has been marked as a duplicate of this bug. ***

Created attachment 97996 [details]
bug buddy report 10/27/2007

Here's the latest from Bug Buddy, This appeared while the screen saver was running. I haven't been able to make the error reproduce itself since I installed the debuggers you have requested me to install. If there is a log file or something that might give more information to you please let me know, I would be more than happy to post it.

Thanks again, Tim. But again, this is the crasher mentioned in comment #59.

Please try to play around in the preferences dialog. Similar bugreports say, that this kind of crasher is trigger by playing around with it.

Are there any usable backtraces for this bug?  Perhaps in one of the dupes?

I installed the -debug RPMs for my distro (Fedora 7) and the problem has not resurfaced.  Figures, right?

Created attachment 98354 [details]
crash 11/01/2007

maybe this one is useful?

Stack trace is good but it's for bug #487253.

This bug appears to be about deallocating the same memory twice.

*** Bug 493580 has been marked as a duplicate of this bug. ***

Created attachment 98687 [details]
Latest crash 

Let's see if this one is it, when is 2.12 going to be available for Fedora 7?

(In reply to comment #75)
> Created an attachment (id=98687) [edit]
> Latest crash 

Debug symbols are all there, but it still looks like a different crash.


> when is 2.12 going to be available for Fedora 7? 

It won't.  Evolution 2.12 will be available in Fedora 8.

Created attachment 98754 [details]
Crash 11/07/2007 

Happened while moving mail from Junk folder

*** Bug 494698 has been marked as a duplicate of this bug. ***

*** Bug 494959 has been marked as a duplicate of this bug. ***

(In reply to comment #76)
> (In reply to comment #75)
> > Created an attachment (id=98687) [edit]
> > Latest crash 
> 
> Debug symbols are all there, but it still looks like a different crash.
> 
> 
> > when is 2.12 going to be available for Fedora 7? 
> 
> It won't.  Evolution 2.12 will be available in Fedora 8.
> 

So does the last log file in comment #77 have what you need? 

> So does the last log file in comment #77 have what you need? 

Yes, that looks like the original stack trace and the debug information is all there.  That should be enough to investigate this further.  Thanks!

Great work Tim! Thanks a lot. I am pasting the stacktrace to support searching.

Matthew: Are there any pango patches on fedora that might cause this crash?

Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 211501056 vsize: 211501056 resident: 106803200 share: 44490752 rss: 106803200 rss_rlim: 4294967295
CPU usage: start_time: 1194395472 rtime: 13510 utime: 9763 stime: 3747 cutime:1120 cstime: 213 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208886544 (LWP 8628)]
[New Thread -1368089712 (LWP 19022)]
[New Thread -1378579568 (LWP 19021)]
[New Thread -1389069424 (LWP 19000)]
[New Thread -1298482288 (LWP 9257)]
[New Thread -1308972144 (LWP 8661)]
[New Thread -1248265328 (LWP 8649)]
0x00110402 in __kernel_vsyscall ()

+ Trace 176978

----------- .xsession-errors (9 sec old) ---------------------
23:48:15 : ---> Package cpio.i386 0:2.6-28.fc7 set to be updated
23:48:15 : ---> Package samba.i386 0:3.0.26a-6.fc7 set to be updated
23:48:15 : ---> Package qt4.i386 0:4.3.2-4.fc7 set to be updated
23:48:15 : ---> Package kernel-devel.i686 0:2.6.22.9-91.fc7 set to be erased
23:48:15 : ---> Package kernel-doc.noarch 0:2.6.23.1-21.fc7 set to be updated
23:48:15 : ---> Package PySolFC.noarch 0:1.1-4.fc7 set to be updated
23:48:15 : ---> Package samba-common.i386 0:3.0.26a-6.fc7 set to be updated
23:48:16 : ---> Package kernel-debug-devel.i686 0:2.6.23.1-21.fc7 set to be installed
23:48:16 : ---> Package hdparm.i386 0:7.7-1.fc7 set to be updated
23:48:21 : Running Transaction
warning: the debug information found in "/usr/lib/debug//usr/lib/libbeagle.so.0.0.0.debug" does not match "/usr/lib/libbeagle.so.0" (CRC mismatch).
Cannot access memory at address 0xfffff7fc
Cannot access memory at address 0xfffff7fc
--------------------------------------------------

(In reply to comment #82)
> Great work Tim! Thanks a lot. I am pasting the stacktrace to support searching.
> 
> Matthew: Are there any pango patches on fedora that might cause this crash?
> 
Your welcome Matt & Tobias, I don't know if this helps but if I run rpm -qa *pango*
pango-1.16.4-2.fc7
pango-devel-1.16.4-2.fc7
pango-debuginfo-1.16.4-2.fc7
ruby-pango-0.16.0-14.fc7
ruby-pango-devel-0.16.0-14.fc7

Also I was able to get this to happen while other programs were running. The programs were Yumex (doing large install/update). I mention this because if you look at most of my attachments it has other activity and my computer freezes when Evo is running and something else is in the foreground. For example if I leave Evo  minimized and run yumex, and let the screen saver launch and let those three run after I go to bed I will have to power cycle the computer. I have a single core processor, if that matters any. 

Good luck with the investigation

(In reply to comment #82)
> Matthew: Are there any pango patches on fedora that might cause this crash?

No, the patches in the Fedora 7 Pango package look pretty harmless.  Behdad himself maintains it.  Frankly I'd be suspicious of GtkHTML long before I'm suspicious of Pango.

The stacktrace looks like a double free of something on the slice allocator.
Could be a reference counting error on a GObject.  I'll see if anything in htmltext.c jumps out at me.

Stared at this for awhile tonight:

A PangoItem contains a PangoAnalysis, and that in turn contains a GSList of extra attributes.  pango_item_free() calls pango_attribute_destroy() on each item in that attribute list and then frees the list itself with g_slist_free().  Somehow the GSList pointer itself is either corrupt or dangling.

I didn't see any obvious errors in htmltext.c but admittedly I can't make heads or tails of most of that code.  I think someone will need to reproduce this under valgrind with the slice allocator disabled (G_SLICE=always-malloc).

Tim: Do you have a particular mail that consistently triggers this crash?  I think I need to reproduce this for myself before I can investigate further.

Putting this back in NEEDINFO for now.

> Tim: Do you have a particular mail that consistently triggers this crash?  I
> think I need to reproduce this for myself before I can investigate further.

 
No there is no specific mail that trips this. The crash seems to be occurring when I move mail from the Junk folder (Spam Assassin) and run a system update.
For example in the crash I posted, I was running an update through Yumex and while waiting for the update to complete I checked my e-mail folders and was moving mail from the Junk mail folder, while it was in the "learning not-junk" mode the crash occurred. 
So I guess the steps to re-create the issue would be:
1) launch Yumex and do an update with Evo minimized
2) while updating the system, Maximize Evo and move mail from Junk folder 
3) Evo Locks up 

*** Bug 492402 has been marked as a duplicate of this bug. ***

*** Bug 461063 has been marked as a duplicate of this bug. ***

*** Bug 488385 has been marked as a duplicate of this bug. ***

*** Bug 490243 has been marked as a duplicate of this bug. ***

*** Bug 491701 has been marked as a duplicate of this bug. ***

*** Bug 492123 has been marked as a duplicate of this bug. ***

*** Bug 498864 has been marked as a duplicate of this bug. ***

*** Bug 499521 has been marked as a duplicate of this bug. ***

*** Bug 501219 has been marked as a duplicate of this bug. ***

*** Bug 500975 has been marked as a duplicate of this bug. ***

*** Bug 495714 has been marked as a duplicate of this bug. ***

Dear Reporter, could you please get us a stacktrace with environment variable G_SLICE set to "debug-blocks", it might help to narrow down the actual
problem.

*** Bug 500816 has been marked as a duplicate of this bug. ***

(In reply to comment #98)
> Dear Reporter, could you please get us a stacktrace with environment variable
> G_SLICE set to "debug-blocks", it might help to narrow down the actual
> problem.
> 

If you could give me instructions on how to do that and where that environment variable is located I would be happy to set that for future crashes. 

(In reply to comment #100)
> If you could give me instructions on how to do that and where that environment
> variable is located I would be happy to set that for future crashes. 

$ G_SLICE=debug-blocks gdb evolution

http://library.gnome.org/devel/glib/unstable/glib-running.html

*** Bug 501606 has been marked as a duplicate of this bug. ***

(In reply to comment #101)
> (In reply to comment #100)
> > If you could give me instructions on how to do that and where that environment
> > variable is located I would be happy to set that for future crashes. 
> 
> $ G_SLICE=debug-blocks gdb evolution
> 
> http://library.gnome.org/devel/glib/unstable/glib-running.html
> 

With what options? if I run the command I get: 
 G_SLICE=debug-blocks gdb evolution
GNU gdb Red Hat Linux (6.6-16.fc7rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) 

if I use help all I get: 
set width -- Set number of characters gdb thinks are in a line
set write -- Set writing into executable and core files
undisplay -- Cancel some expressions to be displayed when program stops
whatis -- Print data type of expression EXP
x -- Examine memory: x/FMT ADDRESS

Command class: files

add-shared-symbol-files -- Load the symbols from shared objects in the dynamic linker's link map
add-symbol-file -- Load symbols from FILE
add-symbol-file-from-memory -- Load the symbols out of memory from a dynamically---Type <return> to continue, or q <return> to quit---
 loaded object file
cd -- Set working directory to DIR for debugger and program being debugged
core-file -- Use FILE as core dump for examining memory and registers
directory -- Add directory DIR to beginning of search path for source files
edit -- Edit specified file or function
exec-file -- Use FILE as program for getting contents of pure memory
file -- Use FILE as program to be debugged
forward-search -- Search for regular expression (see regex(3)) from last line listed
generate-core-file -- Save a core file with the current state of the debugged process
list -- List specified function or line
load -- Dynamically load FILE into the running program
nosharedlibrary -- Unload all shared object library symbols
path -- Add directory DIR(s) to beginning of search path for object files
pwd -- Print working directory
reverse-search -- Search backward for regular expression (see regex(3)) from last line listed
search -- Search for regular expression (see regex(3)) from last line listed
section -- Change the base address of section SECTION of the exec file to ADDR
sharedlibrary -- Load shared object library symbols for files matching REGEXP
symbol-file -- Load symbol table from executable file FILE

---Type <return> to continue, or q <return> to quit---
Command class: internals

flushregs -- Force gdb to flush its register cache (maintainer command)
maintenance -- Commands for use by GDB maintainers
maintenance agent -- Translate an expression into remote agent bytecode
maintenance check-symtabs -- Check consistency of psymtabs and symtabs
maintenance cplus -- C++ maintenance commands
maintenance cplus first_component -- Print the first class/namespace component of NAME
maintenance cplus namespace -- Print the list of possible C++ namespaces
maintenance demangle -- Demangle a C++/ObjC mangled name
maintenance deprecate -- Deprecate a command
maintenance dump-me -- Get fatal error; make debugger dump its core
maintenance info -- Commands for showing internal info about the program being debugged
maintenance info breakpoints -- Status of all breakpoints
maintenance info psymtabs -- List the partial symbol tables for all object files
maintenance info sections -- List the BFD sections of the exec and core files
maintenance info symtabs -- List the full symbol tables for all object files
maintenance internal-error -- Give GDB an internal error
maintenance internal-warning -- Give GDB an internal warning
maintenance packet -- Send an arbitrary packet to a remote target
---Type <return> to continue, or q <return> to quit---
maintenance print -- Maintenance command for printing GDB internal state
maintenance print architecture -- Print the internal architecture configuration
maintenance print cooked-registers -- Print the internal register configuration including cooked values
maintenance print dummy-frames -- Print the contents of the internal dummy-frame stack
maintenance print msymbols -- Print dump of current minimal symbol definitions
maintenance print objfiles -- Print dump of current object file definitions
maintenance print psymbols -- Print dump of current partial symbol definitions
maintenance print raw-registers -- Print the internal register configuration including raw values
maintenance print reggroups -- Print the internal register group names
maintenance print register-groups -- Print the internal register configuration including each register's group
maintenance print registers -- Print the internal register configuration
maintenance print statistics -- Print statistics about internal gdb state
maintenance print symbols -- Print dump of current symbol definitions
maintenance print type -- Print a type chain for a given symbol
maintenance set -- Set GDB internal variables used by the GDB maintainer
maintenance set dwarf2 -- Set DWARF 2 specific variables
maintenance set dwarf2 max-cache-age -- Set the upper bound on the age of cached dwarf2 compilation units
maintenance set profile -- Set internal profiling
---Type <return> to continue, or q <return> to quit---
maintenance show -- Show GDB internal variables used by the GDB maintainer
maintenance show dwarf2 -- Show DWARF 2 specific variables
maintenance show dwarf2 max-cache-age -- Show the upper bound on the age of cached dwarf2 compilation units
maintenance show profile -- Show internal profiling
maintenance show-debug-regs -- Set whether to show variables that mirror the x86 debug registers
maintenance space -- Set the display of space usage
maintenance time -- Set the display of time usage
maintenance translate-address -- Translate a section name and address to a symbol
maintenance undeprecate -- Undeprecate a command

Command class: obscure

checkpoint -- Fork a duplicate process (experimental)
compare-sections -- Compare section data on target to the exec file
complete -- List the completions for the rest of the line as a command
fork -- Fork <n>: Switch between forked processes
monitor -- Send a command to the remote monitor (remote targets only)
process -- Process <pid>: Switch between forked processes
remote -- Send a command to the remote monitor
restart -- Restart <n>: restore program context from a checkpoint
---Type <return> to continue, or q <return> to quit---
stop -- There is no `stop' command

Command class: running

advance -- Continue the program up to the given location (same form as args for break command)
attach -- Attach to a process or file outside of GDB
continue -- Continue program being debugged
detach -- Detach a process or file previously attached
detach checkpoint -- Detach from a fork/checkpoint (experimental)
disconnect -- Disconnect from a target
finish -- Execute until selected stack frame returns
handle -- Specify how to handle a signal
interrupt -- Interrupt the execution of the debugged program
jump -- Continue program being debugged at specified line or address
kill -- Kill execution of program being debugged
next -- Step program
nexti -- Step one instruction
run -- Start debugged program
signal -- Continue program giving it signal specified by the argument
start -- Run the debugged program until the beginning of the main procedure
step -- Step program until it reaches a different source line
stepi -- Step one instruction exactly
---Type <return> to continue, or q <return> to quit---
target -- Connect to a target machine or process
target async -- Use a remote computer via a serial line
target child -- Unix child process (started by the "run" command)
target core -- Use a core file as a target
target exec -- Use an executable file as a target
target extended-async -- Use a remote computer via a serial line
target extended-remote -- Use a remote computer via a serial line
target multi-thread -- Threads and pthreads support
target remote -- Use a remote computer via a serial line
thread -- Use this command to switch between threads
thread apply -- Apply a command to a list of threads
thread apply all -- Apply a command to all threads
until -- Execute until the program reaches a source line greater than the current

Command class: stack

backtrace -- Print backtrace of all stack frames
bt -- Print backtrace of all stack frames
down -- Select and print stack frame called by this one
frame -- Select and print a stack frame
return -- Make selected stack frame return to its caller
select-frame -- Select a stack frame without printing anything
---Type <return> to continue, or q <return> to quit---
up -- Select and print stack frame that called this one

Command class: status

info -- Generic command for showing things about the program being debugged
info address -- Describe where symbol SYM is stored
info all-registers -- List of all registers and their contents
info args -- Argument variables of current stack frame
info auxv -- Display the inferior's auxiliary vector
info breakpoints -- Status of user-settable breakpoints
info catch -- Exceptions that can be caught in the current stack frame
info checkpoints -- IDs of currently known forks/checkpoints
info classes -- All Objective-C classes
info common -- Print out the values contained in a Fortran COMMON block
info copying -- Conditions for redistributing copies of GDB
info dcache -- Print information on the dcache performance
info display -- Expressions to display when program stops
info extensions -- All filename extensions associated with a source language
info files -- Names of targets and files being debugged
info float -- Print the status of the floating point unit
info forks -- IDs of currently known forks/checkpoints
info frame -- All about selected stack frame
info functions -- All function names
---Type <return> to continue, or q <return> to quit---
info handle -- What debugger does when program gets various signals
info line -- Core addresses of the code for a source line
info linkmap -- Display the inferior's linkmap
info locals -- Local variables of current stack frame
info macro -- Show the definition of MACRO
info mem -- Memory region attributes
info proc -- Show /proc process information about any running process
info program -- Execution status of the program
info registers -- List of integer registers and their contents
info scope -- List the variables local to a scope
info selectors -- All Objective-C selectors
info set -- Show all GDB settings
info sharedlibrary -- Status of loaded shared object libraries
info signals -- What debugger does when program gets various signals
info source -- Information about the current source file
info sources -- Source files in the program
info stack -- Backtrace of the stack
info symbol -- Describe what symbol is at location ADDR
info target -- Names of targets and files being debugged
info terminal -- Print inferior's saved terminal status
info threads -- IDs of currently known threads
info tracepoints -- Status of tracepoints
info types -- All type names
---Type <return> to continue, or q <return> to quit---
info variables -- All global and static variable names
info vector -- Print the status of the vector unit
info warranty -- Various kinds of warranty you do not have
info watchpoints -- Synonym for ``info breakpoints''
info win -- List of all displayed windows
macro -- Prefix for commands dealing with C preprocessor macros
macro define -- Define a new C/C++ preprocessor macro
macro expand -- Fully expand any C/C++ preprocessor macro invocations in EXPRESSION
macro expand-once -- Expand C/C++ preprocessor macro invocations appearing directly in EXPRESSION
macro list -- List all the macros defined using the `macro define' command
macro undef -- Remove the definition of the C/C++ preprocessor macro with the given name
show -- Generic command for showing things about the debugger
show annotate -- Show annotation_level
show architecture -- Show architecture of target
show args -- Show argument list to give program being debugged when it is started
show auto-solib-add -- Show autoloading of shared library symbols
show backtrace -- Show backtrace specific variables
show backtrace limit -- Show the upper bound on the number of backtrace levels
show backtrace past-entry -- Show whether backtraces should continue past the en---Type <return> to continue, or q <return> to quit---
try point of a program
show backtrace past-main -- Show whether backtraces should continue past "main"
show backtrace past-zero-pc -- Show whether backtraces should continue past a zero pc value
show breakpoint -- Breakpoint specific settings
show breakpoint pending -- Show debugger's behavior regarding pending breakpoints
show can-use-hw-watchpoints -- Show debugger's willingness to use watchpoint hardware
show case-sensitive -- Show case sensitivity in name search
show charset -- Show the host and target character sets
show check -- Show the status of the type/range checker
show check range -- Show range checking
show check type -- Show type checking
show coerce-float-to-double -- Show coercion of floats to doubles when calling functions
show commands -- Show the history of commands you typed
show complaints -- Show max number of complaints about incorrect symbols
show confirm -- Show whether to confirm potentially dangerous operations
show convenience -- Debugger convenience ("$foo") variables
show copying -- Conditions for redistributing copies of GDB
show cp-abi -- Show the ABI used for inspecting C++ objects
show debug -- Generic command for showing gdb debugging flags
---Type <return> to continue, or q <return> to quit---
show debug arch -- Show architecture debugging
show debug event -- Show event debugging
show debug expression -- Show expression debugging
show debug frame -- Show frame debugging
show debug infrun -- Show inferior debugging
show debug lin-lwp -- Show debugging of GNU/Linux lwp module
show debug observer -- Show observer debugging
show debug overload -- Show debugging of C++ overloading
show debug remote -- Show debugging of remote protocol
show debug serial -- Show serial debugging
show debug solib -- Show debugging status of GNU/Linux shlib module
show debug target -- Show target debugging
show debug-file-directory -- Show the directory where separate debug symbols are searched for
show debugvarobj -- Show varobj debugging
show demangle-style -- Show the current C++ demangling style
show detach-on-fork -- Show whether gdb will detach the child of a fork
show directories -- Current search path for finding source files
show disassembly-flavor -- Show the disassembly flavor
show editing -- Show editing of command lines as they are typed
show endian -- Show endianness of target
show environment -- The environment to give the program
show exec-done-display -- Show notification of completion for asynchronous execu---Type <return> to continue, or q <return> to quit---
tion commands
show extension-language -- Show mapping between filename extension and source language
show follow-fork-mode -- Show debugger response to a program call of fork or vfork
show gnutarget -- Show the current BFD target
show height -- Show number of lines gdb thinks are in a page
show history -- Generic command for showing command history parameters
show history expansion -- Show history expansion on command input
show history filename -- Show the filename in which to record the command history
show history save -- Show saving of the history record on exit
show history size -- Show the size of the command history
show host-charset -- Show the host character set
show inferior-tty -- Show terminal for future runs of program being debugged
show input-radix -- Show default input radix for entering numbers
show language -- Show the current source language
show listsize -- Show number of source lines gdb will list by default
show logging -- Show logging options
show logging file -- Show the current logfile
show logging overwrite -- Show whether logging overwrites or appends to the log file
show logging redirect -- Show the logging output mode
---Type <return> to continue, or q <return> to quit---
show max-user-call-depth -- Show the max call depth for user-defined commands
show opaque-type-resolution -- Show resolution of opaque struct/class/union types (if set before loading symbols)
show osabi -- Show OS ABI of target
show output-radix -- Show default output radix for printing of values
show overload-resolution -- Show overload resolution in evaluating C++ functions
show pagination -- Show state of pagination
show paths -- Current search path for finding object files
show print -- Generic command for showing print settings
show print address -- Show printing of addresses
show print array -- Show prettyprinting of arrays
show print array-indexes -- Show printing of array indexes
show print asm-demangle -- Show demangling of C++/ObjC names in disassembly listings
show print demangle -- Show demangling of encoded C++/ObjC names when displaying symbols
show print elements -- Show limit on string chars or array elements to print
show print max-symbolic-offset -- Show the largest offset that will be printed in <symbol+1234> form
show print null-stop -- Show printing of char arrays to stop at first null char
show print object -- Show printing of object's derived type based on vtable info
---Type <return> to continue, or q <return> to quit---
show print pascal_static-members -- Show printing of pascal static members
show print pretty -- Show prettyprinting of structures
show print repeats -- Show threshold for repeated print elements
show print sevenbit-strings -- Show printing of 8-bit characters in strings as \nnn
show print static-members -- Show printing of C++ static members
show print symbol-filename -- Show printing of source filename and line number with <symbol>
show print union -- Show printing of unions interior to structures
show print vtbl -- Show printing of C++ virtual function tables
show prompt -- Show gdb's prompt
show radix -- Show the default input and output number radices
show remote -- Remote protocol specific variables
show remote P-packet -- Show current use of remote protocol `P' (set-register) packet
show remote X-packet -- Show current use of remote protocol `X' (binary-download) packet
show remote Z-packet -- Show use of remote protocol `Z' packets 
show remote access-watchpoint-packet -- Show current use of remote protocol `Z4' (access-watchpoint) packet
show remote binary-download-packet -- Show current use of remote protocol `X' (binary-download) packet
show remote fetch-register-packet -- Show current use of remote protocol `p' (fe---Type <return> to continue, or q <return> to quit---
tch-register) packet
show remote get-thread-local-storage-address-packet -- Show current use of remote protocol `qGetTLSAddr' (get-thread-local-storage-address) packet
show remote hardware-breakpoint-limit -- Show the maximum number of target hardware breakpoints
show remote hardware-breakpoint-packet -- Show current use of remote protocol `Z1' (hardware-breakpoint) packet
show remote hardware-watchpoint-limit -- Show the maximum number of target hardware watchpoints
show remote memory-map-packet -- Show current use of remote protocol `qXfer:memory-map:read' (memory-map) packet
show remote memory-read-packet-size -- Show the maximum number of bytes per memory-read packet
show remote memory-write-packet-size -- Show the maximum number of bytes per memory-write packet
show remote p-packet -- Show current use of remote protocol `p' (fetch-register) packet
show remote read-aux-vector-packet -- Show current use of remote protocol `qXfer:auxv:read' (read-aux-vector) packet
show remote read-watchpoint-packet -- Show current use of remote protocol `Z3' (read-watchpoint) packet
show remote set-register-packet -- Show current use of remote protocol `P' (set-register) packet
---Type <return> to continue, or q <return> to quit---
show remote software-breakpoint-packet -- Show current use of remote protocol `Z0' (software-breakpoint) packet
show remote supported-packets-packet -- Show current use of remote protocol `qSupported' (supported-packets) packet
show remote symbol-lookup-packet -- Show current use of remote protocol `qSymbol' (symbol-lookup) packet
show remote system-call-allowed -- Show if the host system(3) call is allowed for the target
show remote verbose-resume-packet -- Show current use of remote protocol `vCont' (verbose-resume) packet
show remote write-watchpoint-packet -- Show current use of remote protocol `Z2' (write-watchpoint) packet
show remoteaddresssize -- Show the maximum size of the address (in bits) in a memory packet
show remotebaud -- Show baud rate for remote serial I/O
show remotebreak -- Show whether to send break if interrupted
show remotecache -- Show cache use for remote targets
show remotedevice -- Show device for remote serial I/O
show remotelogbase -- Show numerical base for remote session logging
show remotelogfile -- Show filename for remote session recording
show remotetimeout -- Show timeout limit to wait for target to respond
show remotewritesize -- Show the maximum number of bytes per memory write packet (deprecated)
---Type <return> to continue, or q <return> to quit---
show scheduler-locking -- Show mode for locking scheduler during execution
show serial -- Show default serial/parallel port configuration
show solib-absolute-prefix -- Show prefix for loading absolute shared library symbol files
show solib-search-path -- Show the search path for loading non-absolute shared library symbol files
show step-mode -- Show mode of the step operation
show stop-on-solib-events -- Show stopping for shared library events
show struct-convention -- Show the convention for returning small structs
show substitute-path -- Show the current source path substitution rule
show symbol-reloading -- Show dynamic symbol table reloading multiple times in one run
show target-charset -- Show the target character set
show trace-commands -- Show state of GDB CLI command tracing
show trust-readonly-sections -- Show mode for reading from readonly sections
show tui -- TUI configuration variables
show tui active-border-mode -- Show the attribute mode to use for the active TUI window border
show tui border-kind -- Show the kind of border for TUI windows
show tui border-mode -- Show the attribute mode to use for the TUI window borders
show unwindonsignal -- Show unwinding of stack if a signal is received while in a call dummy
---Type <return> to continue, or q <return> to quit---
show user -- Show definitions of user defined commands
show values -- Elements of value history around item number IDX (or last ten)
show verbose -- Show verbosity
show version -- Show what version of GDB this is
show warranty -- Various kinds of warranty you do not have
show watchdog -- Show watchdog timer
show width -- Show number of characters gdb thinks are in a line
show write -- Show writing into executable and core files

Command class: support

apropos -- Search for commands matching a REGEXP
define -- Define a new command name
document -- Document a user-defined command
dont-repeat -- Don't repeat this command
down-silently -- Same as the `down' command
echo -- Print a constant string
help -- Print list of commands
if -- Execute nested commands once IF the conditional expression is non zero
interpreter-exec -- Execute a command in an interpreter
make -- Run the ``make'' program using the rest of the line as arguments
overlay -- Commands for debugging overlays
overlay auto -- Enable automatic overlay debugging
---Type <return> to continue, or q <return> to quit---
overlay list-overlays -- List mappings of overlay sections
overlay load-target -- Read the overlay mapping state from the target
overlay manual -- Enable overlay debugging
overlay map-overlay -- Assert that an overlay section is mapped
overlay off -- Disable overlay debugging
overlay unmap-overlay -- Assert that an overlay section is unmapped
quit -- Exit gdb
shell -- Execute the rest of the line as a shell command
source -- Read commands from a file named FILE
up-silently -- Same as the `up' command
while -- Execute nested commands WHILE the conditional expression is non zero

Command class: tracepoints

actions -- Specify the actions to be taken at a tracepoint
collect -- Specify one or more data items to be collected at a tracepoint
end -- Ends a list of commands or actions
passcount -- Set the passcount for a tracepoint
save-tracepoints -- Save current tracepoint definitions as a script
tdump -- Print everything collected at the current tracepoint
tfind -- Select a trace frame;
tfind end -- Synonym for 'none'
tfind line -- Select a trace frame by source line
---Type <return> to continue, or q <return> to quit---
tfind none -- De-select any trace frame and resume 'live' debugging
tfind outside -- Select a trace frame whose PC is outside the given range
tfind pc -- Select a trace frame by PC
tfind range -- Select a trace frame whose PC is in the given range
tfind start -- Select the first trace frame in the trace buffer
tfind tracepoint -- Select a trace frame by tracepoint number
trace -- Set a tracepoint at a specified line or function or address
tstart -- Start trace data collection
tstatus -- Display the status of the current trace data collection
tstop -- Stop trace data collection
while-stepping -- Specify single-stepping behavior at a tracepoint

Command class: user-defined


Unclassified commands

unset -- Complement to certain "set" commands
unset environment -- Cancel environment variable VAR for the program
unset substitute-path -- Remove the current source path substitution rule

(In reply to comment #103)
> (In reply to comment #101)
> > (In reply to comment #100)
> > > If you could give me instructions on how to do that and where that environment
> > > variable is located I would be happy to set that for future crashes. 
> > 
> > $ G_SLICE=debug-blocks gdb evolution
> > 
> > http://library.gnome.org/devel/glib/unstable/glib-running.html
> > 
> 
> With what options? if I run the command I get: 
>  G_SLICE=debug-blocks gdb evolution

You also need to follow the instructions at http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running (obviously replacing "gdb name-of-program" with "G_SLICE=debug-blocks gdb evolution").

Created attachment 100365 [details]
from running G_SLICE=debug-blocks gdb evolution

Created attachment 100727 [details]
from my /var/log/messages.2 file 

When I ran the gdb command I had the system lock up on me. I have been looking for the error output until tonight, please let me know if this is of any use in the investigation.

Created attachment 100728 [details]
Latest from bugbuddy 

Bug buddy threw this out, I can't really tell if it related to this issue or not.

*** Bug 498686 has been marked as a duplicate of this bug. ***

*** Bug 503384 has been marked as a duplicate of this bug. ***

*** Bug 504525 has been marked as a duplicate of this bug. ***

*** Bug 505973 has been marked as a duplicate of this bug. ***

Created attachment 102373 [details]
Evolution BugBuddy Output 080108

The bugbuddy error output while working with Evolution this morning.
My current Evolution version is: evolution-2.10.3-4.fc7

Cheers, 
TC

Matthew, can you make anything out of comment #105?

This is fedora specific as far as I can tell so I feel that it's bug 447591 as mentioned in comment #50. Hence I propose the close this bug and reopen it if it occurs in later versions of Evolution.

(In reply to comment #113)
> Matthew, can you make anything out of comment #105?

No, I can't make anything out of that, unfortunately.  If we knew how to consistently reproduce the crash, there's other things I could try (valgrind, G_SLICE=debug-blocks, etc.).


> This is fedora specific as far as I can tell so I feel that it's bug 447591 as
> mentioned in comment #50. Hence I propose the close this bug and reopen it if
> it occurs in later versions of Evolution.

I'm okay with that.  If this starts to occur again with later Evolution versions I think I'd prefer to open a fresh bug.  There's too much bogus information here to sift through.

*** Bug 512319 has been marked as a duplicate of this bug. ***

*** Bug 508105 has been marked as a duplicate of this bug. ***

*** Bug 513012 has been marked as a duplicate of this bug. ***

*** Bug 504644 has been marked as a duplicate of this bug. ***

*** Bug 504712 has been marked as a duplicate of this bug. ***

*** Bug 516615 has been marked as a duplicate of this bug. ***

*** Bug 516980 has been marked as a duplicate of this bug. ***

*** Bug 518565 has been marked as a duplicate of this bug. ***

*** Bug 519748 has been marked as a duplicate of this bug. ***

Closing as per comment #114.

Please report if this occurs in a more recent evolution.

*** This bug has been marked as a duplicate of 447591 ***