pcb@cacs.usl.edu (Peter C. Bahrs) (09/30/90)
There is a simple example discusses in the beginning of Volume 1
of the 2 actor manuals. It is about bar chart drawing. Well
run it and don't type in a numeric value for one of the values
input. The debugger will of course come up and say that
'nil doesn't understand...'
fine, no problem. Of course an application should assign default
values to objects to avoid this. But the debugger should and does
trap this. Note that the debugger runs independent of the application.
What happens is that as various debugger windows come up and down,
areas of the screen need to be refreshed, namely the application that
was in error. The bar chart application gets a draw message and
CABOOM.
It tries to draw via a CALL winfunction with a bad value and screws
the system up....cold boot is needed at times.
I think that the debugger needs to be modified such that an application
being debugged is lock stepped with the debugger. No other message should
be able to be processed while debuging. This is what happens in
dbx when debugging X apps and in codeview when debugging SDK apps.
Any ideas? I thought about putting a boolean object in class object
that the debugger should or something to let an app know to avoid
its command processing loop when the debugger is on???????
Let me know what you think!
/*----------- Thanks in advance... --------------------------------------+
| Peter C. Bahrs |
| The USL-NASA Project |
| Center For Advanced Computer Studies INET: pcb@swamp.cacs.usl.edu |
| 2 Rex Street |
| University of Southwestern Louisiana ...!uunet!dalsqnt!gator!pcb |
| Lafayette, LA 70504 |
+-----------------------------------------------------------------------*/