Subject:
|
Re: legOS - Does it work for you?
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Thu, 31 Dec 1998 12:14:35 GMT
|
Viewed:
|
1300 times
|
| |
|
|
> It might be worth picking up the standard malloc/free and seeing if they
> work any better.
I tried that with the same results. At that point, I added some
debug messages to the malloc and free routines. Using the demo
light-sensor program I wrote down the addresses returned by malloc.
There are only two calls per execi, the process_data structure (AKA pid)
and the stack for process. However, when the program ends and
mm_reaper free is being called with bogus addresses. They are not
the same ones previously returned from the malloc calls. Which
leads me to the conclusion that the task management routines, or
my compiler is not doing the right thing.
My real question, is my gcc setup wrong or does the light-sensor
demo stop working properly for everyone after the 6th time you
toggle the run button on and off?
Ben are you using gcc and Linux to do your development?
|
|
Message has 2 Replies:
 | | Re: legOS - Does it work for you?
|
| (...) From previous embedded development efforts, the first thing to look at when weird things happen is stack overflow. In legOS, interrupt handlers run on the user threads' stack which makes it easier to overflow them. Since thread stacks are (...) (26 years ago, 31-Dec-98, to lugnet.robotics)
|
Message is in Reply To:
| | Re: legOS - Does it work for you?
|
| (...) Hmmm ... not so sure if the task manager is responsible - I have a related (I think) problem if I use static variables - programs that work fine with global variables just lock solid when they are static. Since making them static merely moves (...) (26 years ago, 31-Dec-98, to lugnet.robotics)
|
12 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
