Subject:
|
Re: malloc() bug found -- BAD MEMORY REGION :-(
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Fri, 3 Mar 2000 20:54:55 GMT
|
Viewed:
|
1318 times
|
| |
|
|
In lugnet.robotics.rcx.legos, Martin Cornelius writes:
> Martin Cornelius wrote:
> > i'll go ahead now and check if this fixes my mysterious hangups.
>
> made some tests, and - Yep, it works ! I'd strongly encourage everybody
> experiencing strange hangups to apply the little fix to mm_init() i
> suggested. For me, it makes malloc() and dll work perfectly.
I'm afraid this made no difference for me. I still get dll crashes. My
particular symptom is that if I make a 1 line change to legOS then download it,
it crashes straight away at the next dll. Even if I undo the change, then
rebuild & download legOS, it still crashes. I have one working copy of
legOS.srec which I'm gaurding carefully!
I ran a write/read test on all the memory regions malloc uses, and they all
passed. I've tried to track the problem down with cputw(). As far as I can
tell, the lnp interrupt routine (lnp_integrity_byte) gets called and returns
exactly once. I don't know what happens after that. Maybe the stacks not been
setup so it doesn't return from the interrupt routine? Maybe its getting
corrupted? Where is the stack setup & initialised? Any clues as to what next?
Any suggestions appreciated. Maybe then I can get on with the gdb stub!
|
|
Message has 1 Reply:
Message is in Reply To:
10 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
|
|
|
|
