Mark Ulrich wrote: > Now the error looks different (--enable-debug=full), but I recompiled some > libraries. > I will not investigate further, as we decided to use Gtk 2.8 in Puppylinux > for a while. > Thanks for your help. > I add the latest gdb -results. > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 16384 (LWP 29396)] > 0x405bcc3b in g_slice_alloc () from /usr/lib/libglib-2.0.so.0 > (gdb) backtrace > #0 0x405bcc3b in g_slice_alloc () from /usr/lib/libglib-2.0.so.0 > #1 0x405bcd7e in g_slice_alloc0 () from /usr/lib/libglib-2.0.so.0 > #2 0x405167ff in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0 > #3 0x405037fe in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0 > #4 0x4050304b in g_object_newv () from /usr/lib/libgobject-2.0.so.0 > #5 0x405037a7 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0 > #6 0x40502d0f in g_object_new () from /usr/lib/libgobject-2.0.so.0 > #7 0x0806db83 in thunar_file_get_for_info (info=0x82bc200) > at thunar-file.c:655 > #8 0x0807069b in thunar_folder_infos_ready (job=0x0, infos=0x82ac960, > folder=0x81ed600) at thunar-folder.c:331
Ok, that's clearly a crash in the slice allocator. Do you the latest GLib 2.10/2.12? Benedikt _______________________________________________ Thunar-dev mailing list [email protected] http://foo-projects.org/mailman/listinfo/thunar-dev
