delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-help-bounces using -f |
Date: | Tue, 11 Oct 2011 10:42:55 -0400 |
Message-Id: | <201110111442.p9BEgtk6025142@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | geda-help AT delorie DOT com |
In-reply-to: | <1318338356.29731.2.camel@localhost> (message from Richard Rasker |
on Tue, 11 Oct 2011 15:05:56 +0200) | |
Subject: | Re: [geda-help] PCB segfault - project too big? |
References: | <1318338356 DOT 29731 DOT 2 DOT camel AT localhost> |
Reply-To: | geda-help AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | geda-help AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
I have panels with over 800 elements on them, and an individual board with 412. There are no hard-coded limits in PCB that would affect the number of elements. When you build pcb, there's a pcbtest.sh script in src/ that accepts a -gdb option, which runs pcb in a debugger. Once it crashes, type "where" to find out *where* it crashed. You can run "gnetlist -g pcbfwd" on your schematics to make the script file that pcb is running; at least if you want someone else to look at the problem it's fewer files you need to share (you'd still need to share the pcb and any custom footprints it might need to load) Also, make sure you're testing the latest git version of pcb incase it's something that's already been fixed ;-)
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |