[Thunar-dev] Experimental Thunar Trash tarball

Benedikt Meurer benedikt.meurer at unix-ag.uni-siegen.de
Thu Jul 27 18:24:13 CEST 2006

Björn Martensen wrote:
>>>>and this is the bt from the crash related to expanding Locations:
>>>>#0  0xb79008d7 in g_slice_alloc () from /usr/lib/libglib-2.0.so.0
>>>>#1  0xb7900aa5 in g_slice_alloc0 () from /usr/lib/libglib-2.0.so.0
>>>>#2  0xb79daf1f in g_type_create_instance () from
>>>Hm, did you set G_SLICE=always-malloc? Because the crashes are not in
>>The problem does not seem to be in Thunar, as similar crashes have been
>>reported for 0.3.2beta2, which does not explicitly use the slice
>>allocator, but only gtk, pango, atk & Co. are using the slice allocator
>>(i.e. http://bugzilla.xfce.org/show_bug.cgi?id=2028).
>>It'd be nice if you could locate the invalid free()'s and report it to
>>the appropriate gtk component, as I'm unable to reproduce the problem here.
> Hmm.. it's just that I don't know how to locate those invalid free()'s ;(
> Any hints? Or could you tell me in IRC or so..
> I'm currently in #thunar (baze)
> else, my jid would be baze at amessage.info
> would be nice if you could point me in the right direction of what to do.

You already spotted the invalid free()'s earlier. Now you just need to
make Thunar crash, i.e. run Thunar with

export G_SLICE=always-malloc
export MALLOC_CHECK_=2

and be sure to terminate any running instance first (Thunar -q).

BTW: The trash framework is now committed, so you can use SVN snapshots

> thanks
> Björn


More information about the Thunar-dev mailing list