Problems with RTEMS Debug code calling printf

[VARNEY, Patrick -Syntegra UK]

When the RTEMS debug code finds a problem with the heap or when it displays
walking the heap, it calls printf to do so. However, as this uses malloc and
subsequently rtems_region_get_segment, in the first case the debug again
recognizes a problem with the heap and again calls printf. This happens
indefinitely until the code crashes. In the second case the code crashes
fairly quickly as the heap changes as a result of calling printf so that the
links between blocks are no longer valid. Does anyone have a neat solution
or a bright idea how this might be solved ?

Thanks in advance.

Patrick Varney
Tel. 01932 773576
Mob. 0771 8046 750
email patrick.varney at syntegra.bt.co.uk




********************************************************************

This email may contain information which is privileged or confidential. If you are not the intended recipient of this email, please notify the sender immediately and delete it without reading, copying, storing, forwarding or disclosing its contents to any other person
Thank you

Check us out at http://www.syntegra.com

********************************************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20020614/97e24582/attachment.html>