Quote:
Originally Posted by Toni Wilen
No. Soon there would be hundreds of different breakpoint trigger conditions...
There is already log message, I'll add current PC to message, it should be enough information to find where and when it happens.
I have seen that message ("program tried to step over track 80") few times, some loaders do extra useless step after last track has been read and causes this message if last track was 79.
|
Actually I think a log message is probably more appropriate for this kind of thing anyway.
I noticed that the check for stepping out beyond zero is commented out:
Code:
/* else
write_log (_T("program tried to step beyond track zero\n"));
"no-click" programs does that
*/