|Re: [hatari-devel] DSP breakpoints|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
On sunnuntai 24 elokuu 2014, Douglas Little wrote:
> I think I asked this before and probably got an answer, but now I can't
> find the answer in mail history or the debugger docs :-/ so I'm asking
> I'm trying to use the '--exceptions <list> -D' feature to control the
> events which activate the debugger console. However placing --exceptions
> on the commandline causes Hatari to fail to start - it doesn't recognize
> the command.
--debug or -D Toggle whether CPU exceptions invoke debugger
--debug-except <flags> Exceptions invoking debugger, see '--debug-except
"--debug-except" is support to be given on Hatari command line,
"-D" is better used later from the debugger with "setopt -D" so
that TOS startup exceptions don't invoke debugger.
> Was this feature included in the main release or was the syntax changed
> since it was added?
> Also, I think a new DSP debugging feature was added some months back (by
> Eero?) which lets you print the contents of the 16-word DSP stack. I
> can't seem to find this in the help or docs. It's really useful to have
> if the DSP crashes.
"info" is the command giving information on different HW and other
features. DSP stack you see with "info dsp".