Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.forth Subject: Re: crash Date: Mon, 03 Mar 2014 19:20:55 -0500 Organization: Aioe.org NNTP Server Lines: 34 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:28889 On Mon, 03 Mar 2014 19:01:50 -0500, Bernd Paysan wrote: > George Hubert wrote: >> On Tuesday, February 25, 2014 10:46:24 PM UTC, Rod Pemberton wrote: >>> 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 ... >> >> Actually since base isn't in the range 2-36 then it's an ambiguous >> condition so all forths are correct. > > And what were the hard system lockups? You can ctrl-C bigForth just fine > (you can't ctrl-C xbigforth in the X window, because ctrl-C-ing only > works from the console, but ctrl-C in the starting console works just > fine). > This was for Windows SE. BadExecute and BadReturn for bigForth causes a total and complete system lockup. The only way out was to power down. I.e., No ability to break out via Ctrl-C. No response from GUI. No response from the OS. No ability to use keyboard. No ability to use mouse. No ability to terminate bigForth or any other application. etc. Rod Pemberton PS Someone may need to reply to this for Bernd to see this...