 | | Re: Re: Scheduler patch
|
|
(...) Yea you're right. I wasn't thinking. /Joel (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Breaking from infinite loops
|
|
(...) Hi, if you just want to stop your "own" program use the Forth word ABORT or ABORT" : TEST 1000 0 DO \ do something run-button-down? ABORT" Aborted by user!" LOOP ; or if you want what looks like a "reset" use COLD: run-button-down? IF (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Aborting from ISR
|
|
Ah I see... intriguing idea :) Rereading your original post it should have been quite clear what you wanted. Unfortunately (as far as I know) Mario is right, there doesn't seem to be a clean solution other than manipulating the return stack. I've (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Breaking from infinite loops
|
|
This feels vaguely similar to a question just recently posed, almost. I need a way to get out of a user program that intentionally defines an infinite loop. My best attempt so far at an exit word : exit POWER_OFF LCD_4TH LCD_REFRESH ; in the context (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: detecting memory leaks
|
|
I've been experimenting with memory leak detection in the wake of recent discussions, and have some additional thoughts, including a potential kernel patch issue. This msg is a bit long, appologies. The proposed method of checking for memory leaks (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.legos)
|
