|
From: | Sander van Rijn |
Subject: | Desired behavior for bug #38485: using 'run history' twice |
Date: | Sat, 9 Mar 2013 02:16:12 +0100 |
Fri 08 Mar 2013 06:00:09 AM CET, original submission: Using 'run history' twice in a row leads to a segfault. The first invocation runs the previous command, whatever it was. The second invocation executes the previous command which is 'run history' and an infinite loop is generated. This isn't a common occurrence, but it isn't great behavior by the interpreter either. Sample Code: | disp (1); run history run history |
[Prev in Thread] | Current Thread | [Next in Thread] |