On Sunday, November 1, 2015 at 10:18 PM, Kevin Handy wrote:
> Would it be possible for the error messages to display the fully expanded
> command that caused the error as part of the message!
>
>This would also help debug ini files. Right now you just get an error
> message with no context.
If one is having trouble with some detail of a simh command file and you need
to see the complete flow of how a command file is processed, the command file
can always be invoked with verify or verbose mode enabled:
sim> do -v some-command-file.ini
With verbose mode enabled, each command in the file is echoed prior to its
execution (along with the filename and line number) immediately before any
messages (error or otherwise) which the command may produce.
The default command file (which will automatically be processed when a
simulator starts (called {simulator-name}.ini or simh.ini)) OR a command file
explicitly mentioned on the simulator command line can also be displayed if the
simulator is invoked with the -v switch specified on the command line.
As for the suggestion that the command which caused an error message to be
generated be displayed without regard to the verbose mode when processing
command files, well it already does that. This is new since simh v3.9.
- Mark
_______________________________________________
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
