[Info-vax] DCL, was: Re: Microkernel

[VAXman- at SendSpamHere.ORG]

In article <k0j9po$bv5$1 at dont-email.me>, Stephen Hoffman <seaohveh at hoffmanlabs.invalid> writes:
>On 2012-08-16 14:24:51 +0000, Jose Baars said:
>
>> Op donderdag 16 augustus 2012 14:54:59 UTC+2 schreef (onbekend) het volgende:
>>> You can still specify your OWN CLI in your UAF record!
>> 
>> Are there any examples including sources of this available somewhere?
>
>FWIW, I don't know of any.  And I don't see any posted, based on a 
>cursory search.
>The sys$cli call and the related supervisor-mode APIs aren't officially 
>documented.
>What documentation that is available here is in the source listings and 
>in the IDSM.
>DEC/shell and MCR sources never got released, and gnv isn't implemented 
>as a CLI.

Neither of which would have any bearing on this.  SYS$CLI is merely
a callback to the DCL handler for things like setting symbols, etc.
There's no SYS$CLI callback for the DCL RECALL buffer.  

THe issue is a matter of $IMGACT/$IMGFIX and building an image which
uses these to map DCL.EXE.  You then setup the OOB AST on the control
character of your choice and read the DCL recall buffer.  I'm busy at
the moment working on my own "DCL" wrapper for a DCL debugger.  WHEN
and or IF I get some free time, I may document the mechanism.  It's
really not all that difficult.  Simple system services and a little
flag in the .OPT when linking. ;)  Of course, you can't expect to use
any RTLs because you can't activate/share/merge them.


-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.