Initializing the debugging code- August 23, 2007 With yesterday's changes, the unmanaged debugging API has changed. If you're embedding Mono and want to initialize the debugging API, you only need to call mono_debug_init () - the old mono_debug_init_1() etc. hacks are now all gone (caution: do not call mono_debug_init_corlib()). mono_debug_init() needs to be called before the first appdomain is created - after that, everything will go automatically.http://primates.ximian.com/~martin/blog/entry_172.html Domain unloading and identifying threads- August 22, 2007 Today, I committed two important bug fixes in the debugger which both required a lot of code changes. The most important user-visible change is that the debugging info is now stored on a per-appdomain basis - which means that it can be freed when the domain gets unloaded. We can now also unload symbol files. This required quite some changes - both in the runtime and in the debugger. This wasn't only important to save memory, but also for correctness and robustness: When a domain gets...http://primates.ximian.com/~martin/blog/entry_171.html Domain unloading and the debugging code- August 8, 2007 Yesterday, I got an important and interesting bug report: We currently do not support domain unloading in the new debugging code. This means that when a domain is unloaded, we do not free the debugging info. To make things worse, some internal hashtables also contain references to the MonoMethod 's which will lead to crashes later on. Freeing the debugging info is not so easy since the debugger may access it at any time, so we need to tell the debugger first. However, I got a really good...http://primates.ximian.com/~martin/blog/entry_170.html |