[Evolution-hackers] Re: [Evolution] wombat going berserk
- From: Chris Toshok <toshok ximian com>
- To: Ron Smits <rons ronsmits com>
- Cc: Ron Smits <ron ronsmits com>, evolution ximian com, evolution-hackers ximian com
- Subject: [Evolution-hackers] Re: [Evolution] wombat going berserk
- Date: 21 Apr 2003 01:55:08 -0700
Ah, this crash is fixed in CVS.
Chris
On Mon, 2003-04-21 at 00:22, Ron Smits wrote:
> Chris
>
> The behaviour has changed and will now make the wombat process die on an
> assert, I have cut and pasted the gdb stuff, I will try and get a
> berserking wombat later
>
> Ron
>
> gal_view_instance_set_current_view_id: view_id set to Work_Week_View
> gal_view_instance_set_current_view_id: view_id set to Work_Week_View
>
> (evolution-1.3:503): Bonobo-CRITICAL **: file bonobo-ui-component.c:
> line 1323 (impl_exists): assertion `container != CORBA_OBJECT_NIL'
> failed
>
> (evolution-1.3:503): Bonobo-CRITICAL **: file bonobo-ui-component.c:
> line 1323 (impl_exists): assertion `container != CORBA_OBJECT_NIL'
> failed
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to Thread 1024 (LWP 505)]
> 0x40ed5161 in g_logv (log_domain=0x80cd41c "wombat-pas",
> log_level=G_LOG_LEVEL_ERROR, format=0x80cd6a0 "file %s: line %d (%s):
> assertion failed: (%s)",
> args1=0xbffff370) at gmessages.c:504
> 504 gmessages.c: No such file or directory.
> in gmessages.c
> (gdb) bt
> #0 0x40ed5161 in g_logv (log_domain=0x80cd41c "wombat-pas",
> log_level=G_LOG_LEVEL_ERROR, format=0x80cd6a0 "file %s: line %d (%s):
> assertion failed: (%s)",
> args1=0xbffff370) at gmessages.c:504
> #1 0x40ed5219 in g_log (log_domain=0x80cd41c "wombat-pas",
> log_level=G_LOG_LEVEL_ERROR, format=0x80cd6a0 "file %s: line %d (%s):
> assertion failed: (%s)")
> at gmessages.c:527
> #2 0x080619fe in pas_backend_file_get_uri (backend=0x817a6c0) at
> pas-backend-file.c:1488
> #3 0x080b915b in pas_backend_get_uri (backend=0x817a6c0) at
> pas-backend.c:64
> #4 0x080b61e1 in backend_last_client_gone_cb (backend=0x817a6c0,
> data=0x8115930) at pas-book-factory.c:151
> #5 0x080b6558 in pas_book_factory_process_request (factory=0x8115930,
> request=0x81df018) at pas-book-factory.c:305
> #6 0x080b65fc in pas_book_factory_process_queue (factory=0x8115930) at
> pas-book-factory.c:340
> #7 0x40ed06e6 in g_idle_dispatch (source=0x81df068, callback=0x80b65dc
> <pas_book_factory_process_queue>, user_data=0x8115930) at gmain.c:3164
> #8 0x40ecdfc9 in g_main_dispatch (context=0x8109de8) at gmain.c:1653
> #9 0x40ecede7 in g_main_context_dispatch (context=0x8109de8) at
> gmain.c:2197
> #10 0x40ecf1c3 in g_main_context_iterate (context=0x8109de8, block=1,
> dispatch=1, self=0x80e7468) at gmain.c:2278
> #11 0x40ecf89f in g_main_loop_run (loop=0x812ab78) at gmain.c:2498
> #12 0x40c32a7f in bonobo_main () at bonobo-main.c:293
> #13 0x0805f529 in main (argc=3, argv=0xbffff6a4) at wombat.c:245
> #14 0x410f017d in __libc_start_main (main=0x805f398 <main>, argc=3,
> ubp_av=0xbffff6a4, init=0x805d264 <_init>, fini=0x80ccd40 <_fini>,
> rtld_fini=0x4000a534 <_dl_fini>, stack_end=0xbffff69c) at
> ../sysdeps/generic/libc-start.c:129
> (gdb) frame 3
> #3 0x080b915b in pas_backend_get_uri (backend=0x817a6c0) at
> pas-backend.c:64
> 64 return (* PAS_BACKEND_GET_CLASS (backend)->get_uri)
> (backend);
> (gdb) print *backend
> $1 = {parent_object = {g_type_instance = {g_class = 0x81846e8},
> ref_count = 1, qdata = 0x0}, priv = 0x81df018}
> (gdb) print *backend->priv
> $2 = {clients = 0x0, loaded = 0, writable = 0}
> (
>
> On Sat, 2003-04-19 at 05:37, Chris Toshok wrote:
> > On Thu, 2003-04-17 at 14:23, Ron Smits wrote:
> > > running evolution 1.3.2 with openldap 2.0.9 trying to schedule a meeting
> > > will make wombat go mad. It will eat all memory and swap.
> > >
> > > Attached is a compressed strace of the wombat process
> >
> > If this is easy for you to reproduce, could you run wombat in gdb and
> > get a stack trace when things start going wrong?
> >
> > Chris
> >
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]