[Thunar-dev] Thunar + Hal

[Benedikt Meurer]

Jannis Pohlmann wrote:
> I updated from SVN and when starting Thunar, I get this:
> 
> jannis at nebelsee ~/devel/xfce/thunar> gdb thunar
> 
> ...
> 
> (gdb) run
> Starting program: /usr/local/bin/thunar
> [Thread debugging using libthread_db enabled]
> [New Thread -1219656000 (LWP 20005)]
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1219656000 (LWP 20005)]
> 0xb7727289 in free () from /lib/tls/i686/cmov/libc.so.6
> (gdb) backtrace
> #0  0xb7727289 in free () from /lib/tls/i686/cmov/libc.so.6
> #1  0xb75e2f2b in libhal_free_string_array () from /usr/lib/libhal.so.1
> #2  0xb7eb3f29 in thunar_vfs_volume_manager_hal_init
> #(manager_hal=0x814bbc8) at thunar-vfs-volume-hal.c:785

Uhm, it crashes while trying to free the result of
libhal_drive_find_all_volumes(). According to the implementation of
libhal_drive_find_all_volumes(), the result will either be NULL or a
malloc()'ed array of strdup()'ed UDIs terminated with a NULL pointer.
Exactly what can be passed to libhal_free_string_array(). Which version
of HAL do you use?

Benedikt