On Tue, 2011-08-23 at 23:22 +0530, Abhijit Kshirsagar wrote: > Thanks. I will try with the newer version. > As of now I think the problem lies in one of the custom components I'm > using - but that should still not cause a segfault right?` No - it should not. If you can still reproduce it in a newer gEDA version (or can find instructions to reproduce it reliably at your end with a minimal test-case), perhaps you could send us a copy of component causing the problem and we can investigate the problem further. > Also, I'd have liked some inputs on how to debug the problem. Is > there some way of enabling "debug" logging or something? Not that I recall. Running under "gdb" gdb --args pcb path_to_your_pcb_file.pcb then getting a backtrace with the "bt"<ENTER> command when it crashes might be useful. Running under "valgrind" valgrind pcb path_to_your_pcb_file.pcb Would be very slow, but is excellent at nailing the root cause of memory corruption problems which lead to crashes. Again - checking if you can reproduce the issue under a later gschem version is probably the most efficient way to proceed. -- 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