Re: gnome-panel sometimes freezes during aptitude upgrade
On Wed, 2007-06-27 at 11:39 +0200, Gabor Gombas wrote:
> On Tue, Jun 26, 2007 at 05:21:40PM +0200, Michel Dänzer wrote:
>
> > ==14840== Conditional jump or move depends on uninitialised value(s)
> > ==14840== at 0x100252D0: (within /usr/bin/gnome-panel)
> > ==14840== by 0xF333B18: g_cclosure_marshal_VOID__VOID (in /usr/lib/libgobject-2.0.so.0.1200.12)
> > ==14840== by 0xF322DC8: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.1200.12)
> > ==14840== by 0xF337370: (within /usr/lib/libgobject-2.0.so.0.1200.12)
> > ==14840== by 0xF338678: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.1200.12)
> > ==14840== by 0xF338848: g_signal_emit (in /usr/lib/libgobject-2.0.so.0.1200.12)
> > ==14840== by 0xF974258: ensure_valid_themes (gtkicontheme.c:1208)
> > ==14840== by 0xF9743F0: _gtk_icon_theme_check_reload (gtkicontheme.c:3107)
> > ==14840== by 0xFB1B1EC: gtk_window_client_event (gtkwindow.c:4872)
> > ==14840== by 0xF9B81F0: _gtk_marshal_BOOLEAN__BOXED (gtkmarshalers.c:84)
> > ==14840== by 0xF321008: (within /usr/lib/libgobject-2.0.so.0.1200.12)
> > ==14840== by 0xF322DC8: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.1200.12)
> >
> >
> > Does that ring any bells, or (how) can I get more information out of
> > valgrind?
>
> My feeling is that this is a false positive (which is very often the
> case with "unitialized value" warnings from valgrind). If anything
> inside the icon_theme structure at gtkicontheme.c:1208 would be really
> uninitialized you'd get some kind of error much earlier.
I'm a valgrind newbie, but doesn't the above indicate the problem is
somewhere in /usr/bin/gnome-panel, not at gtkicontheme.c:1208?
> Btw. did you use "--partial-loads-ok=yes"? That can avoid some of the false positives
> (and in some rare cases can miss valid errors, but I doubt that would be
> the case with gnome-panel).
I don't think I need it until there's too many of the above cluttering
up the output, but I'll keep it in mind, thanks.
> If there were no messages relating to SIGSEGV or invalid read/write,
> then I think you did not manage to trigger the bug this time.
Okay, I'll keep trying. Note that bug #430630 didn't crash when running
in valgrind either, though it did flag the invalid memory access.
--
Earthling Michel Dänzer | http://tungstengraphics.com
Libre software enthusiast | Debian, X and DRI developer
Reply to: