http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660He did not know that fusion was involved. http://ayende.com/4289/debugging-win32-crash-in-nh-prof#comment3http://ayende.com/4289/debugging-win32-crash-in-nh-prof#comment3Fri, 13 Nov 2009 13:11:42 GMTI would have suggested to enable fusion logging to capture the possible binding failures. [http://msdn.microsoft.com/en-us/library/e74a18c4](http://msdn.microsoft.com/en-us/library/e74a18c4)(VS.71).aspx http://ayende.com/4289/debugging-win32-crash-in-nh-prof#comment2http://ayende.com/4289/debugging-win32-crash-in-nh-prof#comment2Fri, 13 Nov 2009 10:52:10 GMTThis is strange, I've got an error dialog with the "BindingFailure" text in it whenever I run the latest build (544 I think). I have no clue why you only get native stack. http://ayende.com/4289/debugging-win32-crash-in-nh-prof#comment1http://ayende.com/4289/debugging-win32-crash-in-nh-prof#comment1Fri, 13 Nov 2009 10:33:31 GMT