Re: Application crash

["Ishii Satoshi" <sat_ishii hotmail com>]

> > My application crashes after working for about a month. It works fine 
for 
> > the time being. 
> > The core shows gtk part only except main. 
> > gtk version is 2,4. 
> >
> > Does anyone know how I can debug this kind of case? 
>
> If you mean the app was running for a month continuously and
> then crashed, not much can be done.

Some machines works continuously over a month, but crashed in some more 
days.
That is, some crashes in 20days, the other did in 30 or 40 days etc.

> If your distro has -debuginfo, -debug, -dbg, or how they're
> called, packages with debugging info you can try to install
> them to get more information from gdb.  Find out what event
> it was, what was the object involved, function args, etc.

Thanks. I'm trying.

> Except that this stack trace...
>
> > #0  0xb7c22a9a in g_object_remove_weak_pointer () from 
> > /usr/lib/libgobject-2.0.so.0 
> > #1  0xb7d02d61 in expose_serial_predicate () from 
> > /usr/lib/libgdk-x11-2.0.so.0 
> > #2  0xb7d030a5 in expose_serial_predicate () from 
> > /usr/lib/libgdk-x11-2.0.so.0 
> > #3  0xb7cfcb9d in gdk_x11_register_standard_event_type () from 
> > /usr/lib/libgdk-x11-2.0.so.0 
> > #4  0xb7cfd6fd in gdk_x11_register_standard_event_type () from 
> > /usr/lib/libgdk-x11-2.0.so.0 
> > #5  0xb7cfd891 in gdk_x11_register_standard_event_type () from 
> > /usr/lib/libgdk-x11-2.0.so.0 
> > #6  0xb7bb2e4a in g_main_depth () from /usr/lib/libglib-2.0.so.0 
> > #7  0xb7bb3f28 in g_main_context_dispatch () from 
/usr/lib/libglib-2.0.so.0 
> > #8  0xb7bb4260 in g_main_context_dispatch () from 
/usr/lib/libglib-2.0.so.0 
> > #9  0xb7bb48a3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 
> > #10 0xb7e39403 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 
> > #11 0x0809f138 in main (argc=1, argv=0xbfffe664) at main.cc:252 
>
> ...is bogus.  At least all the stuff from
> gdk_x11_register_standard_event_type() upward.  Either the
> stack was overwritten, or the debug info does not match the
> binaries.  Hm, is your program multithreaded?  Anyway, I
> don't understand the Glib main loop locking code, so I
> cannot tell what could go wrong there.

The debug info should match. If so, do you think the stack was corrupt?
I have some core file and the stack is always the same. If corrupt, is this 
possible?

Now I'm checking code again and use valgrind.

BR
S.Ishii

_________________________________________________________________
一番乗り! Windows Vista、 2007 Office system の情報はここから 
http://www.microsoft.com/japan/msc/