Erratic errors with evolution-2.26

Peter Ulrich Kruppa ulrich at pukruppa.net
Mon Apr 20 19:18:01 UTC 2009


Am Montag, den 20.04.2009, 15:14 -0400 schrieb Joe Marcus Clarke:
> On Mon, 2009-04-20 at 21:06 +0200, Peter Ulrich Kruppa wrote:
> > Am Montag, den 20.04.2009, 14:38 -0400 schrieb Joe Marcus Clarke:
> > > On Mon, 2009-04-20 at 20:35 +0200, Peter Ulrich Kruppa wrote:
> > > > Am Montag, den 20.04.2009, 13:37 -0400 schrieb Joe Marcus Clarke: 
> > > > > On Mon, 2009-04-20 at 19:25 +0200, Peter Ulrich Kruppa wrote:
> > > > > > Hi,
> > > > > > 
> > > > > > since I am using evolution-2.26, bug-buddy will _sometimes_ be started
> > > > > > when an email arrives. It says an unknown application failed and
> > > > > > delivers a trace like this one:
> > > > > 
> > > > > This isn't a stack trace.  You need to run Evolution in gdb, then follow
> > > > > the documentation at http://www.freebsd.org/gnome/docs/bugging.html to
> > > > > get a real stack trace with debugging symbols when the crash occurs.
> > > > I tried that, but I don't believe it will be of any use, since it isn't
> > > > evo itself that crashes - bug-buddy says it doesn't know this crashing
> > > > application.
> > > > 
> > > > Anyway, I ran evo from gdb and got this:
> > > > -------------------------------------
> > > > (gdb) run
> > > > Starting program: /usr/local/bin/evolution 
> > > > [New LWP 100159]
> > > > [New Thread 0x809f020b0 (LWP 100159)]
> > > > /home/ulrich/.gtkrc-2.0:2: Include-Datei konnte nicht gefunden werden:
> > > > ».gtkrc-2.0-scrollbar_cog«
> > > > ** (evolution:57108): DEBUG: mailto URL command: evolution %s
> > > > ** (evolution:57108): DEBUG: mailto URL program: evolution
> > > > [New Thread 0x809f03050 (LWP 100173)]
> > > > [New Thread 0x809f031e0 (LWP 100174)]
> > > > [New Thread 0x809f03370 (LWP 100177)]
> > > > [New Thread 0x809f03690 (LWP 100178)]
> > > > [New Thread 0x809f03820 (LWP 100188)]
> > > > [New Thread 0x809f03cd0 (LWP 100190)]
> > > > [Thread 0x809f03370 (LWP 100177) exited]
> > > > [Thread 0x809f03cd0 (LWP 100190) exited]
> > > > [New Thread 0x809f03ff0 (LWP 100205)]
> > > > [New Thread 0x809f04180 (LWP 100206)]
> > > > [New Thread 0x809f04310 (LWP 100207)]
> > > > [New Thread 0x809f044a0 (LWP 100208)]
> > > > [Thread 0x809f03ff0 (LWP 100205) exited]
> > > > [Thread 0x809f04310 (LWP 100207) exited]
> > > > [Thread 0x809f044a0 (LWP 100208) exited]
> > > > [Thread 0x809f04180 (LWP 100206) exited]
> > > > [New Thread 0x809f03370 (LWP 100177)]
> > > > [New Thread 0x809f03cd0 (LWP 100190)]
> > > > [Thread 0x809f03370 (LWP 100177) exited]
> > > > [Thread 0x809f03cd0 (LWP 100190) exited]
> > > > [New Thread 0x809f03ff0 (LWP 100177)]
> > > > [Thread 0x809f03ff0 (LWP 100177) exited]
> > > > [New Thread 0x809f04310 (LWP 100177)]
> > > > [New Thread 0x809f044a0 (LWP 100190)]
> > > > [New Thread 0x809f04180 (LWP 100205)]
> > > > [New Thread 0x809f05da0 (LWP 100206)]
> > > > [New Thread 0x809f05f30 (LWP 100207)]
> > > > [Thread 0x809f05f30 (LWP 100207) exited]
> > > > [New Thread 0x809f060c0 (LWP 100207)]
> > > > [Thread 0x809f060c0 (LWP 100207) exited]
> > > > [Thread 0x809f05da0 (LWP 100206) exited]
> > > > [New Thread 0x809f03370 (LWP 100206)]
> > > > [Thread 0x809f03370 (LWP 100206) exited]
> > > > [New Thread 0x809f03cd0 (LWP 100206)]
> > > > [Thread 0x809f03cd0 (LWP 100206) exited]
> > > > [New Thread 0x809f03ff0 (LWP 100206)]
> > > > [New Thread 0x809f05f30 (LWP 100207)]
> > > > [New Thread 0x809f060c0 (LWP 100208)]
> > > > [Thread 0x809f05f30 (LWP 100207) exited]
> > > > [New Thread 0x809f05da0 (LWP 100207)]
> > > > [Thread 0x809f04310 (LWP 100177) exited]
> > > > [Thread 0x809f060c0 (LWP 100208) exited]
> > > > [Thread 0x809f03ff0 (LWP 100206) exited]
> > > > [Thread 0x809f05da0 (LWP 100207) exited]
> > > > [New Thread 0x809f03370 (LWP 100177)]
> > > > [New Thread 0x809f03cd0 (LWP 100206)]
> > > > [Thread 0x809f03cd0 (LWP 100206) exited]
> > > > [New Thread 0x809f05f30 (LWP 100206)]
> > > > [Thread 0x809f05f30 (LWP 100206) exited]
> > > > [New Thread 0x809f04310 (LWP 100206)]
> > > > [Thread 0x809f04310 (LWP 100206) exited]
> > > > [New Thread 0x809f060c0 (LWP 100206)]
> > > > [Thread 0x809f060c0 (LWP 100206) exited]
> > > > [Thread 0x809f03370 (LWP 100177) exited]
> > > > 
> > > > Program exited normally.
> > > > (gdb) thread apply all bt
> > > > (gdb) quit
> > > > -------------------------------------------------------
> > > > 
> > > > When an email arrived and bug-buddy came up, I finished evo.
> > > > 
> > > > I wonder: Could it be one of evo's plugins that trigger the
> > > > crash-message - or some other dependent application? 
> > > 
> > > Start Evo, then attach gdb to it.  See if you get a back trace in gdb
> > > then.
> > Doesn't look any different (to me):
> 
> Nothing I can suggest, then.  It looks like an integer overflow, but
> without a back trace, it will be difficult to track down.
Bad luck,
but big thanks for your effort!

Greetings

Uli.

> 
> Joe
> 


More information about the freebsd-gnome mailing list