Nigel Spon

Debugger can't find MSL source

Discussion created by Nigel Spon on Jul 13, 2006
Latest reply on Jul 13, 2006 by Nigel Spon
CW for ColdFire, v6.2. Is the debugger meant to be able to step into the MSL source? It switches to assembly every time I do so, it doesn't seem to be able to find the source. I have "Store Full Path Names" turned on, and the debugger finds the source of a library I have built just fine. I can't see what is different about MSL. I can successfully build the MSL library that I am using, and I have tried turning on "A6 stack frames", but to no avail...

I'm actually trying to understand alloc.c so I can figure out how to write free-memory and largest-block routines that scan the heap - if this has already been done somewhere I would love to know...

Thanks for any assistance,