Re: gEDA: gnetlist ERROR: Stack overflow

[Ales Hvezda <ahvezda-at-NOSPAMseul_dot_org>]

Hi Dave,


[snip]
>Since there seems to be two stack limits (eval which defaults to 22000 machine
>words and debug which defaults to 20000 machine words), I've added the followi
>ng
>two lines to my copy of gnet-pads.scm:
>
>(debug-options (list 'stack 200000))
>(eval-options (list 'stack 220000))


	Yeah, I don't get any more stack overflows either with the sample
you sent out.  I put those commands in my local gnetlistrc (or you could
put them into ~/.gEDA/gnetlistrc) and that worked too.  Stefan has address
some of the root of this problem, so these options will hopefully not be
permanently necessary.


[snip]
>Because I wanted to leave the option open to isolate grounds on three parts of
> the
>board, I defined two extra ground symbols and nets, DGND and RFGND (in additio
>n to
>the default GND).  I attached them all to one mounting hole, because for now, 
>I
>don't think I need isolated grounds.  In this configuration, gnetlist crashes.


	That's not good.  Hmmm.. lemme try something.  Nope that little test
didn't crash on me.  One word of warning with this though, gnetlist will
rename nets (created via the net= attribute) into one common netname
if you start tying things together.  There is a way of control this,
but I've never been 100% convinced I'm doing the right thing.  So,
if you see some odd behavior let me know.


>  If
>I edit the DGND and RFGND symbols and change the nets from DGND and RFGND to j
>ust
>GND, gnetlist no longer crashes.  So I have the netlist that I need, but I'm a
>fraid
>there is a latent bug in gnetlist.?
>
>If I have time, I will try to make a non-proprietary schematic that causes the
> core
>dump.  For now, all I can provide is the debugger backtrace, which is below.


	That would be greatly appreciated and will make my debugging go
much much much faster.  Thanks for the bug reports.

									-Ales