[Mono-dev] Access violation when debugger is attached

Jonathan Chambers joncham at gmail.com
Mon Aug 30 22:02:57 EDT 2010

      Mono uses access violations to implement null reference exceptions on
Windows (IIRC). Mono handles these normally during program flow. However,
when the debugger is attached it handles them before mono can. I don't know
of a way to avoid this behavior. Normally, I just issue an assert in the
area I want to debug and then attach with the debugger. This may be the
issue you are having, but I don't know if an exception during mono_jit_init
is normal.


On Mon, Aug 30, 2010 at 7:12 PM, Chris Robison <chrisdrobison at gmail.com>wrote:

> I'm working on an interesting project when I'm using a project called
> Firebreath to create an NPAPI browser plugin which loads an embedded mono
> runtime to do things we want to do. To test this app, I'm attaching Visual
> Studio to all the Chrome processes and stepping through things. What's
> happening is that when the debugger is attached the mono_jit_init call
> causes a seg fault. When it is not attached things work fine. Has anyone
> ever run into that?
> Chris Robison
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20100830/4e5d2a65/attachment.html 

More information about the Mono-devel-list mailing list