Comments on: Crashing Like VB http://www.davinciunltd.com/2007/11/crashing-like-vb/ Jim McKeeth's blog on creative and innovative Delphi programming. Wed, 07 Oct 2009 22:04:39 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: Jim McKeeth http://www.davinciunltd.com/2007/11/crashing-like-vb/comment-page-1/#comment-88 Jim McKeeth Tue, 04 Dec 2007 05:41:56 +0000 http://www.davinciunltd.com/2007/11/crashing-like-vb/#comment-88 Great thanks Allen! No yelling from me, that is for sure. JITEnable is a cool feature if I ever feel the need to crash like VB. Great thanks Allen! No yelling from me, that is for sure. JITEnable is a cool feature if I ever feel the need to crash like VB.

]]> By: Allen Bauer http://www.davinciunltd.com/2007/11/crashing-like-vb/comment-page-1/#comment-77 Allen Bauer Wed, 28 Nov 2007 19:00:18 +0000 http://www.davinciunltd.com/2007/11/crashing-like-vb/#comment-77 Jim, I have a funny feeling that I'm going to get yelled at here :-). There is a one-line built-in solution to the above problem. Many releases ago, I had taken into account that folks may want to invoke the built-in Windows error reporting or to allow a Just-in-Time debugger to be invoked when an exception is raised. Down inside the system unit, there is a global byte variable called JITEnable. Simply set it to 1 to tell the exception system to pass all non-Delphi exceptions on through to the UnhandledExceptionFilter API, which is what will invoke either the registered JIT debugger or Windows error reporting. You can also set this value to >1 which will pass *all* exceptions raised to that API. This is a little different than the solution you propose above where it is only exceptions that percolate to the base handler that are passed off to the OS. If they're caught and handled elsewhere, the OS will never know about them. With the JITEnable technique, the exception is passed along at any point exceptions are handled. Allen. Jim,

I have a funny feeling that I’m going to get yelled at here :-) . There is a one-line built-in solution to the above problem. Many releases ago, I had taken into account that folks may want to invoke the built-in Windows error reporting or to allow a Just-in-Time debugger to be invoked when an exception is raised.

Down inside the system unit, there is a global byte variable called JITEnable. Simply set it to 1 to tell the exception system to pass all non-Delphi exceptions on through to the UnhandledExceptionFilter API, which is what will invoke either the registered JIT debugger or Windows error reporting. You can also set this value to >1 which will pass *all* exceptions raised to that API.

This is a little different than the solution you propose above where it is only exceptions that percolate to the base handler that are passed off to the OS. If they’re caught and handled elsewhere, the OS will never know about them. With the JITEnable technique, the exception is passed along at any point exceptions are handled.

Allen.

]]>