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

[Ales Hvezda <ahvezda@xxxxxxxxxxxxxx>]

[snip]
>	So, I ran valgrind against gschem and it generated the following
>error (in a different part of the code):
>

	Oops, forgot to mention how to reproduce the problem.  Basically
just run gschem and place a single string into the schematic.  That will
cause valgrind to complain.  Just opening up gschem and exiting without
adding any strings does not cause the memory deallocation error.  

for the curious, here is how I run valgrind:

valgrind -v --leak-check=yes --show-reachable=yes gschem file.sch > err 2>&1


								-Ales