Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Segfaulting script
- X-seq: zsh-workers 22498
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Segfaulting script
- Date: Sat, 17 Jun 2006 21:47:33 -0700
- In-reply-to: <20060617181417.GA19721@xxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20060613231505.GA23239@xxxxxxxxxxxx> <20060616110319.GB2780@xxxxxxxxxxxxxxx> <060617101117.ZM32743@xxxxxxxxxxxxxxxxxxxxxx> <20060617181417.GA19721@xxxxxxxxxxxxxxx>
On Jun 17, 8:14pm, Frank Terbeck wrote:
}
} > You can't assign values to an array in a "local" statement.
}
} Yes, I know that the assignment does not make sense.
Certainly. I was just pointing out for the peanut gallery exactly what
went wrong.
} > My guess would be that you get a segfault when the compile-time
} > setting of the maximum function depth is large enough that you run
} > out of memory before the limit is hit. There's not a whole lot we
} > can do about that.
}
} Hm, definitely no nice, but I trust your judgement.
It might be possible to estimate a run-time value for the recursion
depth based on ulimit sizes, but some OSs are willing to overpromise on
memory allocations in the hope that all that was asked for will never
really be used. In such a case there's no way to avoid the segfault if
more is used than truly is available.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author