Re: gEDA-user: problems with PCB and large board

[gene <carzrgr8@xxxxxxxxxxxxx>]

Peter Clifton wrote:
> Ok, hold that thought for a moment..
> 
> Try the attached patch (should fix the issue).
> Valgrind is a wonderful tool ;)
> 
> If it stops the crash, could you just confirm for me that valgrind is
> then happy, and doesn't report any problems.
> 
> Best wishes,
>>

Thanks Peter, it works!  I also have the first patch installed as well. 
  Here's the output from valgrind:

gene@geno:~/avTek/hardware/schematic$ cat pcblog.stdout
gene@geno:~/avTek/hardware/schematic$ cat pcblog.stderr
==5440== Memcheck, a memory error detector.
==5440== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==5440== Using LibVEX rev 1854, a library for dynamic binary translation.
==5440== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==5440== Using valgrind-3.3.1, a dynamic binary instrumentation framework.
==5440== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==5440== For more details, rerun with: -v
==5440==
==5440==
==5440== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 191 from 3)
==5440== malloc/free: in use at exit: 24,489,918 bytes in 120,756 blocks.
==5440== malloc/free: 741,760 allocs, 621,004 frees, 276,167,310 bytes 
allocated.
==5440== For counts of detected errors, rerun with: -v
==5440== searching for pointers to 120,756 not-freed blocks.
==5440== checked 24,531,988 bytes.
==5440==
==5440== LEAK SUMMARY:
==5440==    definitely lost: 118,254 bytes in 11,638 blocks.
==5440==      possibly lost: 622,518 bytes in 713 blocks.
==5440==    still reachable: 23,749,146 bytes in 108,405 blocks.
==5440==         suppressed: 0 bytes in 0 blocks.
==5440== Rerun with --leak-check=full to see details of leaked memory.
gene@geno:~/avTek/hardware/schematic$



Merry Christmas!

gene


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user