| ??? 04/29/02 16:14 Read: times |
#22275 - RE: Sleeping Bugs in the code: - more |
In systems with a display and room for this luxury, I even make Crash() read the stack, reset the stack and then display all registers and the calling address.
Erik |
| Topic | Author | Date |
| Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: - more | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: - more | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: - more | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: - more | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: Sleeping Bugs in the code: | 01/01/70 00:00 | |
| RE: crash() | 01/01/70 00:00 | |
| RE: crash() | 01/01/70 00:00 | |
RE: Sleeping Bugs in the code: | 01/01/70 00:00 |