| |
Do you guys have an established mechanism for debugging?
I'm thinking of writing certain numbers to the display using cputw().
The idea being that the number frozen forever on the display will be the
(approximately) last place the code was ok before the RCX got wedged. I
do this on larger systems with printf frequently.
I'm reasonably sure cputw will work, but if there are better ways, I'm
open to suggestions. I can't test my code in gdb, because it depends on
interrupts. Well, I could, but it might be more painful than the cputw
method.
|
|
Message has 1 Reply:
 | | Re: Debugging
|
| (...) That's the method I've used. Just be sure to put an lcd_refresh() after the cputw() call - I can't remember if cputw() does the lcd_refresh() or not. Another thing I've done is write out a number where the upper byte indicates a position in (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.legos)
|
7 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
