CodeWarrior Coldfire debugger



Hi All;

I'm debugging an MCF5485-based project. I would like to know how to
determine what area of memory is being used by the BDM debugger. Obviously
if I check the exceptions tabs for certain event handlers to be handled by
the debugger, the debugger must place code in target memory. For the
exceptions this is not difficult to find, but I am concerned that other
memory areas may be in use that I am trying to use as well. For instance, I
am unable to successfully use the second bank of core sram successfully.
Everytime I try to place the system stack there (0x20001000-0x20002000) the
debugger refuses to step into my code. I know I have the registers set up
correctly for using that bank in the same fashion as bank 1. So I am
guessing that maybe the debugger wishes to use that space. I can't find any
info from PEMICRO.COM.

Thanks!


.



Relevant Pages

  • Re: MyString Class
    ... > I compiled your program and run it under the debugger. ... > The first crash happens in ... ... > memory is flawed. ... First bug fixed. ...
    (comp.lang.cpp)
  • RE: Memory increasing even when in debug-break
    ... there are 2 types of memory leak in .Net: ... More interesting is the debugger breaks while memory still increasing ... Microsoft Online Community Support ...
    (microsoft.public.vsnet.debugging)
  • Re: Question about workitem.
    ... I set SynchronizationScope to WdfSynchronizationScopeNone. ... A fatal system error has occurred. ... Debugger entered on first try; Bugcheck callbacks have not been invoked. ... Invalid system memory was referenced. ...
    (microsoft.public.development.device.drivers)
  • Re: How is possible that NDIS_PACKET->Head->MappedSystemVa is page
    ... Also try and enable NDIS debug tracing, ... "NDIS Driver Debugging Guidelines" ... NDIS Debug Tracing and Kernel Debugger Extensions" ... Amazing is that address of memory referenced is inside of NDIS_PACKET: ...
    (microsoft.public.development.device.drivers)
  • Re: virtual memory leak? (was: Re: strange problem.....)
    ... and after some time I break this connection. ... executable in heap analyser and still there are no traces of memory ... The debugger is exceedingly programmable, too, ... I'm not a particular fan of malloc and free, ...
    (comp.os.vms)