Command line interpretation

As mentioned before supports only ``vanilla'' command line without any extension schemes. Other compilers, like gcc, may expect something different and there could be some disagreements about an interpretation of a command line. Usually this can be fixed quite easily. Here is a file, named fixargs.adb, which can be used with a command line following this pattern

where <program> was compiled by gcc. fixargs.adb This file defines some function keys. The fact that commands associated with keys F14 and F15 do not exist, even if they are referenced in a line for F1, is not harmful in any way. You may define these keys later for your advantage. After started hit F1 followed by Return. This will cause, among others, an execution of a command attached to F11, i.e F1–shifted. This command will set a breakpoint at a start of real program with a fixup command attached. In turn, this will modify your stack causing your program to see proper arguments. Requests in a form of <sp,10/x are added only for reassurance and to show what really happens.

The example above assumes that a symbol getitime is defined in your program. Replace with something which is really present or you will see some error messages. They are not fatal. All of this is not going to work if main is not present in your symbol table. This is not really likely for a program which has a symbol table and was compiled from C sources, but may happen for other languages. Modify accordingly.