Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.forth Subject: Re: crash Date: Tue, 25 Feb 2014 17:46:24 -0500 Organization: Aioe.org NNTP Server Lines: 45 Message-ID: References: <530b79a4$0$2907$e4fe514c@news2.news.xs4all.nl> <530b7fc7$0$2830$e4fe514c@news2.news.xs4all.nl> <530c9b43$0$2960$e4fe514c@news2.news.xs4all.nl> NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.16 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.forth:28777 On Tue, 25 Feb 2014 08:31:57 -0500, Hans Bezemer wrote: > I'd prefer people would add their codes and comments, like Marcel did, > before adding results. These are probably not the latest versions of these Forths. Also, the data should be confirmed by someone else prior to use. If you use this data, I'd prefer to *not* have my name placed on the webpage. Compiler | Bad Execute | Bad Address | Bad Align | Bad Return | Bad Code | Bad Res1 | Bad Res2 | Bad Break | Bad Numb bigForth 2.4.0 | -18 | -2 | 0 | -18 | -7(1) | -2 | -2 | -16 | 0 Gforth 0.7.0 ITC | -2 | -2 | 0 | -2 | -7(1) | -2 | -2 | -2 | -2 Win32Forth 6.14.02 | -2(2) | -2(2) | 0 | -2(2) | -2(2) | -2(2) | -2(2) | -16 | -6(3) Remark 1: a) result code -7 plus reports location, or result code -2 plus empties dictionary b) also - WORDS did not display the dictionary but BYE worked - so other words might too Remark 2: result code -2 plus continues at another prompt prior to returning to Forth prompt Remark 3: not an infinite loop - prints one, then loops for a while printing zeroes, but stops If the messages printed any diagnostic information other than the error message, I assumed it was result code -2 and not result code -3. I'm not sure how to test for result code -20. It's interesting to note that bigForth appeared to worked correctly for the BadNumb test. It displayed '1' and stopped. Of course, it has two hard system lockups ... NOTE: Win32Forth hangs consistently, after the second use of WORDS ... e.g., BadAddress .S WORDS BadAddress .S WORDS <--hangs e.g., BadReturn .S WORDS BadReturn .S WORDS <--hangs etc. Rod Pemberton