Call stack

  • Thread starter Thread starter Rastio Hodul
  • Start date Start date
R

Rastio Hodul

Hi,
does anyone know how does VS.NET debugger construct call stack for CF
application?
My understanding is that CLR has a debugging engine built in it and that
includes functions to construct the call stack. I have seen the article
(http://msdn.microsoft.com/library/default.asp?url=/msdnmag/issues/02/11/clr
debugging/toc.asp) which describes how to build the debugger for full
framework.
I believe it is possible to do it for CF - MS has done it.

Can anyone point me to any relevant information?

Thanks,
 
This is done externally by the debugger, which has internal knowledge of the
..NET CF execution engine implementation. In the desktop framework it is
exposed to the user. In the CF implementation details are private and not
accessible to you
 
Thanks for the answer.

The knowledge of the .NET CF execution engine implementation is exactly what
I need. I would like to write my own StackTrace class in CF, which would be
able to provide the call stack on runtime while CF is not connected to PC.
Is this doable, even if I have to do it in C++?
 
I would also find this info useful. Or, more to the point of what we would
like to see, is the ability to trap or log exception details when they are
thrown. Without the StackTrace property of the Exception class, it's
difficult to find those hard-to-reproduce exceptions that occur on a
tester's machine. A tool or setting, etc. that could be used to somehow
capture the origin of the exception would be extremely useful in building
solid commercial applications.

Bill
 
Back
Top