On Sun, 2007-09-09 at 08:24 -0500, Harold D. Skank wrote: > On Sat, 2007-09-08 at 11:16 -0400, DJ Delorie wrote: > > > What I find is that frequently when I start a job (most recently miter), > > > the job starts OK, then the monitor shows that memory consumption starts > > > to grow until I see of the order of 99.0-99.5% memory commitment. > > > > Any messages in the console? Like, warnings about a big undo buffer? > > Nothing, the job just continues to run with all the memory consumed and > the swap growing. It appears that the machine is spending all of it's > time moving memory around. > Harold Skank
Try (with a backup copy of your design saved) running the operation again; but start PCB with: gdb --args pcb <anything else for PCB's command line> then type "run" (enter) quickly after starting the operation which is eating all memory, switch back to your terminal running the gdb debugger, and hit Ctrl-C to stop the program. type "backtrace" (enter) And cut-paste the list here. This should let the -devs know what code is actually being executed when the problem occurs. It might be obvious from reading the code, I'm not sure - however often a backtrace will help. Regards, - 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!) _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user