|
From: | Juergen Sauermann |
Subject: | Re: [Bug-apl] Deep Nesting |
Date: | Mon, 24 Aug 2015 15:41:05 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 |
Hi, the segfault thrown by this stack limit is not caught even though GNU APL installs signal handlers for SIGSEGV. Therefore anything based on evaluating the arguments of the signal handler would not work. The alternative of checking beforehand has (negative) runtime implications and apparently portability issues. I therefore believe that this type of error is so uncommon that we should not handle it. I made a simple test with good old bash in a xterm with recursive call to itself: source ./qqq # qqq is a text file containing only this line A short moment and this does not only crash (in a nice way like throwing a segfault), but kills the xterm with it. In other words, the behaviour of processes when they reach there limits is fairly unpredictable anyhow. As a consequence, I believe it is better to leave things as they are. /// Jürgen On 08/23/2015 07:18 PM, Blake McBride
wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |