I have read the docs concerning memory (stack, dynamic heap, etc) but some details are missing. I'm using GCC so some of these are specific to the compiler; others are generic. 1) If I have a 64K code limit, is that the compile size, link size or prc size? I have already worked around the 32k limit. My code0001 size is 44K. But my prc is 60k. 2) I have seen apps larger than 100k. How do they get around 64k code limit? Or is that just a GCC limit. Re: The next two questions. I have an app that is behaving oddly. It is displaying some garbage characters in a field. Everything worked fine up to my last version. Something I have changed recently, has caused this odd behavior. I'm suspecting stack overflow or dynamic heap limitation. I'm having problems determining how to resolve if either of these two are the cause. I remove a level of nesting of function calls and that changes, but does not fix the problem. 3) If I am suspecting a stack overflow problem, would that get picked up by POSE? Or phrased another way, if I have an app that I suspect has a stack overflow and it runs fine (no POSE errors, just the odd behavior) on POSE does that rule out a stack overflow problem? 4) Same for dynamic heap. If the app runs fine (no POSE errors, just the odd behavior) does that rule out a dynamic heap problem? Is there a tip sheet or something somewhere that gives some specifics on what one can do to conserve stack and dynamic heap? Mike ---------------------------------------------------- Shoot-to-Win Protect the 2nd Amendment ----------------------------------------------------
