[Thunar-dev] ThunarVfsInfo: Bug in thunar_vfs_info_new_for_path?
Benedikt Meurer
benedikt.meurer at unix-ag.uni-siegen.de
Wed Feb 1 17:27:44 CET 2006
Jannis Pohlmann wrote:
> HORRAY! No idea how you found out that *this* caused the problem.
> Impressive, really.
On a linux box:
grep LARGEFILE /usr/include/sys/*.h
[...]
/usr/include/sys/types.h:#if defined __USE_LARGEFILE64 && !defined
__ino64_t_defined
/usr/include/sys/types.h:#if defined __USE_LARGEFILE64 && !defined
__off64_t_defined
[...]
*SCREAM*
open /usr/include/sys/types.h and recognize that ino_t has no fixed size
on Linux/i386, but depends on whether largefile support is active.
Thunar is compiled with largefile support, your program wasn't, so for
your program the compiler got the wrong offset for path in ThunarVfsInfo
and *BOOM*.
I'll commit a workaround.
> - Jannis
Benedikt
More information about the Thunar-dev
mailing list