madshi.net

I have selected the Resource Leak option in the Mad Except options, but the report is not created when I close down the application. This is a Delphi Tokyo 10.2.3 64 bit desktop application. I haven't had this occur before with other apps.

Any ideas?

Many thanks - that was it

When we worked through the webbroker issues a while back I thought I spotted something that looked like I could set a template for what was returned to the browser, rather than the default bug report. Now I look I can't seem to fond what I was looking at then. Can anyone point in the right direction...

I mean do I use the NewException function (as in the example I gave) or should I do something else?

I'm sure I used to do this in an old application but can't find it now. How do you force MadExcept to save the bug report within an exception handler? This is in a webbroker application. Do create a new exception e.g. Try .... Except on E: Exception do begin MadExcept.NewException(etNormal, E).SaveB...

We are having some occasional issues with a server application and Mad captures the exception but truncates the message ... well I think it is MAD that does, you might tell me other wise, although when we step through the code forcing a similar exception we can see the whole message. Here is an exam...

I don't think you need any more ideas

Sorry I've taken so long to try this.

I think it might be too late to WriteClient there. It is called and isapiBugReport is populated (so s1 looks fine), but it is not returned to the browser.

Yes, that's what happens InterceptHttpExtensionProc : HSE_STATUS_PENDING = 3 Exception Raised InterceptServerSupportFunction : HSE_REQ_DONE_WITH_SESSION = 4 (same value as HSE_STATUS_ERROR would be in InterceptHttpExtensionProc ) In InterceptServerSupportFunction isapiBugReport is set and BugReportH...

first step is if @HttpExtensionProcNext <> nil then begin AmHttpServer := true; New(IRSection); InitializeCriticalSection(IRSection^); end; then the call to InterceptHttpExtensionProc.HttpExtensionProcNext(ecb2); returns 3 (HSE_STATUS_PENDING) and isapiBugReport = '', so s1 also = '' then isapiBugRe...

Yes, doesn't seem to get called within InterceptHttpExtensionProc. That completes and then the exception is raised. I can only think that it is to do with that status being HSE_STATUS_PENDING when it is in that proc and not HSE_STATUS_ERROR. I'll have another step through tomorrow and see if I can s...

Yes it does go to that and when the procedure returns, isapiBugReport does have the report.

Is it that InterceptHttpExtensionProc is called first and that is what writes to the client?

Yes, it does go into InterceptISAPIHandleException. The process step through is InterceptHttpExtensionProc <debugger exception notification shows> then InterceptISAPIHandleException and that calls HandleException (showReport = '') and that calls ReceiveHandleException where if showReport <> nil then...

without madexcept it definitely calls TISAPIApplication.ISAPIHandleException, but not when madexcept is loaded when it jumps straight into MadExcept, but with the HSE Pending flag.

Also isapiBugReport is empty

1. Yes, Exception handler was found: 15:18:41-593 madExcept.ISAPIApp_TISAPIApplication_ISAPIHandleException: $00005728 15:18:41-598 Web.Win.ISAPIApp.TISAPIApplication.ISAPIHandleException: $00165aa4 ... 15:31:17-681 madExcept.ISAPIApp_TISAPIApplication_ISAPIHandleException: $00005728 15:31:17-685 We...