On Tue, Nov 24, 2009 at 10:24:55PM +0000, Peter Clifton wrote: > This bug "probably" relates to a back-end which has poor recursion > practice, and ends up using a lot of execution stack to produce the > netlist for a complex design. > > You will need to know which specific backend, and which design - was > used in order to confirm / deny whether this bug still exists. (I recall > "some" backends have been improved to use less stack space.) ---end quoted text---
Nicklas: can you tell us which backend caused your problem ? Also please send the design that caused this issue. Also, I sent this message a few days ago, and (as usual) I forgot to CC the bug submitter (which is you this time): Can this be tested again using geda-gnetlist 1.4.3, against guile 1.8.7 (which is currently in Debian) please ? Or can someone give me steps needed to reproduce the problem ? Note, earlier I tested gnetlist as follows: gnetlist -g protelII -o /tmp/test.net TwoStageAmp.sch And I didn't get any problems. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 (@ subkeys.pgp.net) GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
