Re: gEDA: gEDA/gaf 20050313 almost ready, but not released...

[Ales Hvezda <ahvezda@xxxxxxxxxxxxxx>]

Hi Patrick,

[snip]
>No in fact we do not need it: when the hash table is created the free
>function for its values is specified (o_text_basic.nw:207). This
>g_free can be removed (or remove the one in the hash table
>definition). My fault, sorry.


	Excellent.  I have removed that extra g_free(...) and now gschem
does not seem to hang on exit anymore.  I will spent today banging on the
code with and without valgrind and see what happens.  Thanks for the 
bug fix.

>
> > I'm hoping that this is the cause of the malloc hang.
>
>I am not familiar with valgrind: in a case of double free, does it
>report the first free or the second? The one you point should be
>called first.

	It reports both and yes, I believe the extra g_free was reported
as the first and then the other reported g_free was one that glib was
doing.  I have learned to trust valgrind after it found several very
serious problems for me. :)

								-Ales