gEDA-dev: Valgrind results

[Ales Hvezda]

Hi PeterB,

> A couple of memory leaks for everyone to look at in gschem.  Other than 
> these, gschem currently looks pretty good.

Thanks for running this.

> ==23604== 1,955 bytes in 127 blocks are definitely lost in loss record 150 of 
> 190
> ==23604==    at 0x4005400: malloc (vg_replace_malloc.c:149)
> ==23604==    by 0x46ABF875: g_malloc (in /lib/libglib-2.0.so.0.1200.9)
> ==23604==    by 0x46AD2ED8: g_strdup (in /lib/libglib-2.0.so.0.1200.9)
> ==23604==    by 0x8086CC5: get_main_menu (x_menus.c:200)

Hmmm.. I'm not seeing why this is leaking or I've reached that point 
in awakeness where obvious code isn't obvious anymore.  Plus, I can't
see this leak with my run of valgrind.

> ==23604==
> ==23604==
> ==23604== 2,301 bytes in 53 blocks are definitely lost in loss record 157 of 
> 190

Yup, this one is a real leak.  Fixed in CVS now.  

Thanks,
-Ales