[MonoDevelop] debuging variable

Lluis Sanchez lluis@ximian.com
Tue, 03 May 2005 14:32:05 +0200


This message is shown when an exception is thrown while dispatching a
call through the GUI thread. When this happens, the stack trace of the
exception only includes the frames from the GUI thread, but not the
frames of the thread that originated the call.

If you define the MONODEVELOP_DISPATCH_DEBUG environment variable (for
example, running "export MONODEVELOP_DISPATCH_DEBUG=1" in a console and
starting MonoDevelop from there), then MD will capture the call stack
for every call dispatched through the GUI thread, and will print it in
case of error, so you can see where does the call come from. This option
is disabled by default because capturing the stack trace for every such
call is slow and not usually needed.

Lluis.

On dt, 2005-05-03 at 14:14 +0200, David Makovský wrote:
> Hi all,
> I've just tried to work with debugger inside MD and I got this error:
> Caller stack not available. Define the environment variable
> MONODEVELOP_DISPATCH_DEBUG to enable caller stack capture.
> via Google I found nothing about it and if I tried define it as a /tmp
> dir I got null reference exception. Someone please explain whats about
> and how to use it, it would be helpful.
> 
> Thanks
> 
> David