Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!amdcad!sun!pitstop!sundc!seismo!uunet!mcvax!inria!rouaix
From: rouaix@inria.UUCP (Francois Rouaix)
Newsgroups: comp.sys.amiga
Subject: Re: CON: lockup on typing * <CR> at CLI prompt
Summary: executing *
Message-ID: <605@inria.UUCP>
Date: 11 Jan 88 09:25:02 GMT
References: <279@dana.UUCP>
Organization: INRIA, Rocquencourt. France
Lines: 22

In article <279@dana.UUCP>, rap@dana.UUCP (Rob Peck) writes:
> Yesterday, Harv Laser asked me a question:
>     "Why does the CLI lockup solidly if you just type
> 	* <CR>
> Is the console trying (and succeeding at) executing
> itself?  (It really gets killed, it seems).  :-) :-) :-)

	Yes indeed !!
	I think CLI is trying to execute *, that is the file *.
	But file * is current input, so it will terminate only on a
	ctrl-\ . Ok. So type * <CR>, some junk , and then ctrl-\.
	You should get the error message "file is not an object module".
	Note that if you could manage that the junk you type in matches
	hunk definitions and some binary code, you may execute some
	instructions.


-- 

*- Francois Rouaix                 //       When the going gets tough,       *
*- rouaix@inria.inria.fr         \X/           the guru goes meditating...   *
*- SYSOP of Sgt. Flam's Lonely Amigas Club. (33) (1) 39-55-84-59 (Videotext) *