On Sun, Oct 07, 2007, Josselin Mouette wrote:
> Or maybe what you mean is that it should be freed by gnome_vfs_shutdown.
> I'll change the patch to that effect.
I don't know whether gnome_vfs_shutdown() would be the place to free,
but perhaps the g_strdup()s can be saved altogether in
gnome_vfs
Le dimanche 07 octobre 2007 à 12:17 +0200, Loïc Minier a écrit :
> On Sun, Oct 07, 2007, Josselin Mouette wrote:
> > Or maybe what you mean is that it should be freed by gnome_vfs_shutdown.
> > I'll change the patch to that effect.
>
> I don't know whether gnome_vfs_shutdown() would be the place
Le dimanche 07 octobre 2007 à 11:28 +0200, Loïc Minier a écrit :
> On Sat, Oct 06, 2007, Josselin Mouette wrote:
> > It shouldn't, as it is a static variable, so it should retain its same
> > value between calls.
>
> Why shouldn't it be freed? This will probably give errors within
> valgrind wh
On Sat, Oct 06, 2007, Josselin Mouette wrote:
> It shouldn't, as it is a static variable, so it should retain its same
> value between calls.
Why shouldn't it be freed? This will probably give errors within
valgrind when tracing any program using gnome-vfs.
--
Loïc Minier
Le samedi 06 octobre 2007 à 20:58 +0200, Loïc Minier a écrit :
> Package: gnome-vfs2
> Version: 1:2.20.0-2
> Severity: normal
>
> Hi,
>
> While reading 24_home_dir_fakeroot, it came to my attention that it
> seems to leak memory: g_get_home_dir() returns a const gchar that one
> doesn'
Package: gnome-vfs2
Version: 1:2.20.0-2
Severity: normal
Hi,
While reading 24_home_dir_fakeroot, it came to my attention that it
seems to leak memory: g_get_home_dir() returns a const gchar that one
doesn't have to g_free(), but gnome_vfs_get_home_dir() g_strdup()s it
or g_strdup()s g
6 matches
Mail list logo
