|
Toni Martinez-Colom wrote:
>
> I saw the same behavior some time ago when I worked on a pretty fat program
> (about 6KB compiled code). Sometimes it worked OK, then I removed my debug
> code (some cputs defined by macros) and it hanged miserably... I thought it
> was some kind of pointer error, but after reading your posts I'm not very
> sure of that... Perhaps some kind of linker (dll) error?
currently i believe there is some really subtle bug in malloc(), that
shows up only under special circumstances. I experience similar problems
with a fat kernel/application that disappear after adding one cputw(),
making the binary a little bigger in size.
I have a 100% reproduceable way to hang my RCX during dll'ing after the
deletion stage, and found so far that it's caught in an endless loop
inside malloc().
--Martin
|
|
Message is in Reply To:
| | Re: Odd behavior
|
| I saw the same behavior some time ago when I worked on a pretty fat program (about 6KB compiled code). Sometimes it worked OK, then I removed my debug code (some cputs defined by macros) and it hanged miserably... I thought it was some kind of (...) (25 years ago, 28-Feb-00, to lugnet.robotics.rcx.legos)
|
6 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|