Re: debugging gtk-engines?

On Thu, 2007-08-30 at 23:02 +0200, Jan de Groot wrote:
> With the latest gtk-engines 2.11 clearlooks engine, I get an invalid
> free on running any wxgtk application. This error is caught by glibc,
> which stops the program with a SIGABORT. This error does not happen when
> reverting to the 2.10 package, or when using a different theme engine
> like Mist.
> All I get in this trace is an internal function of wxGTK, which seems to
> call g_free. There's no reference to any theme engine in the valgrind
> output and/or glibc assertion backtrace.
> Do we have any ways to debug these problems in gtk engines?
> The error when using wxgtk applications (vlc in this case) with
> clearlooks 2.11:

That function in wxGTK does this:

g_free( default_border );

It shouldn't call g_free, but gtk_border_free.

Ross Burton                                 mail: ross burtonini com
                                          jabber: ross burtonini com
 PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]