Date: Mon, 20 Apr 2009 21:21:04 +0200 From: Peter Ulrich Kruppa <ulrich@pukruppa.net> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: FreeBSD-Gnome <freebsd-gnome@freebsd.org> Subject: Re: Erratic errors with evolution-2.26 Message-ID: <1240255264.57627.9.camel@pukruppa.net> In-Reply-To: <1240254854.1356.139.camel@shumai.marcuscom.com> References: <1240248302.1533.22.camel@pukruppa.net> <1240249042.1356.91.camel@shumai.marcuscom.com> <1240252515.57389.3.camel@pukruppa.net> <1240252696.1356.122.camel@shumai.marcuscom.com> <1240254362.57627.7.camel@pukruppa.net> <1240254854.1356.139.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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:=20 > > > > > On Mon, 2009-04-20 at 19:25 +0200, Peter Ulrich Kruppa wrote: > > > > > > Hi, > > > > > >=20 > > > > > > since I am using evolution-2.26, bug-buddy will _sometimes_ be = started > > > > > > when an email arrives. It says an unknown application failed an= d > > > > > > delivers a trace like this one: > > > > >=20 > > > > > 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.ht= ml to > > > > > get a real stack trace with debugging symbols when the crash occu= rs. > > > > I tried that, but I don't believe it will be of any use, since it i= sn't > > > > evo itself that crashes - bug-buddy says it doesn't know this crash= ing > > > > application. > > > >=20 > > > > Anyway, I ran evo from gdb and got this: > > > > ------------------------------------- > > > > (gdb) run > > > > Starting program: /usr/local/bin/evolution=20 > > > > [New LWP 100159] > > > > [New Thread 0x809f020b0 (LWP 100159)] > > > > /home/ulrich/.gtkrc-2.0:2: Include-Datei konnte nicht gefunden werd= en: > > > > =C2=BB.gtkrc-2.0-scrollbar_cog=C2=AB > > > > ** (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] > > > >=20 > > > > Program exited normally. > > > > (gdb) thread apply all bt > > > > (gdb) quit > > > > ------------------------------------------------------- > > > >=20 > > > > When an email arrived and bug-buddy came up, I finished evo. > > > >=20 > > > > I wonder: Could it be one of evo's plugins that trigger the > > > > crash-message - or some other dependent application?=20 > > >=20 > > > Start Evo, then attach gdb to it. See if you get a back trace in gdb > > > then. > > Doesn't look any different (to me): >=20 > 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. >=20 > Joe >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1240255264.57627.9.camel>