 | | Re: is it possible to remove lnp_handler while running ?
|
|
"kenneth johansen" <kennethj@stud.cs.uit.no> wrote in message news:3D343FAA.172476....uit.no... (...) I imagine you could just do something like lnp_addressing_set_handler( PORT, (lnp_addressing_handler_t) NULL ); I'm also curious as to why (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | is it possible to remove lnp_handler while running ?
|
|
another dumb question about lnp:) i was wondering if it possible to do something like lnp_addressing_remov...,handler); as opposed to lnp_addressing_set_h...,handler); after much debugging i think i have traced my problem to the fact that (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
I have been thinking (and toying with some ideas) concerning tthe wakeup checking. It might be possible to do wakeup checking more often then between each timeslice. This would make msleep more accurate and provide better sensor handling. I know (...) (22 years ago, 16-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | 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: 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)
|
