On Wed, 2011-02-23 at 21:26 -0600, John Griessen wrote: > On 02/23/2011 09:09 PM, John Griessen wrote: > > ==32105== Whatever the reason, Valgrind cannot continue. Sorry. > > > > Seems like the problem may not even be related to pcb... > > But it's triggered by pcb. The swap amount grows fast at first, then when > about 3GB of RAm is used the rate slows to only 4 or so MB every other 2 secs. > Every other time it goes down, but overall increases til it runs out. > > That's why it segfaults at 1.5 minutes. > > Is this kind of thing coming from compiler, or hardware, or? We have a winner from git bisect: 089fbaf59c78fe75475db737e7e2827cd745d570 is the first bad commit commit 089fbaf59c78fe75475db737e7e2827cd745d570 Author: Newell Jensen <pillar2012@xxxxxxxxx> Date: Sun Jan 23 01:46:53 2011 -0500 Initial C++ compatibility patch Doesn't cover lesstif or batch hids. Makes source code build without warnings on C, and build with warnings on C++. I do wish people would test their refactoring patches... -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ geda-user mailing list geda-user@xxxxxxxxxxxxxx http://www.seul.org/cgi-bin/mailman/listinfo/geda-user