Did madExcept cause this exception?

delphi package - automated exception handling

Did madExcept cause this exception?

Postby lizhengdao » Wed Jul 25, 2018 5:58 am

It's quite strange that the except thread is madExcept itself.
What can I do to avoid this from happening?

Code: Select all
exception number   : 1
exception class    : EAccessViolation
exception message  : Access violation at address 753DA078 in module 'msvcrt.dll'. Read of address 12AA6000.

thread $22c4:
753da078 +04a msvcrt.dll
753da006 +1ac msvcrt.dll             memmove
004a90a9 +00d MPTool.exe   madExcept CallThreadProcSafe
004a910e +032 MPTool.exe   madExcept ThreadExceptFrame
76d8343b +010 kernel32.dll           BaseThreadInitThunk
>> created by thread $198c at:
753e139c +06e msvcrt.dll             _beginthreadex
Attachments
bugreport.zip
full bug report madExcept generated
(8.72 KiB) Downloaded 12 times
lizhengdao
 
Posts: 1
Joined: Wed Jul 25, 2018 5:51 am

Re: Did madExcept cause this exception?

Postby madshi » Wed Jul 25, 2018 6:47 am

It's not strange at all. madExcept will be listed as part of every thread callstack. The reason for that is that madExcept has to hook itself into every thread, to be able to catch and report the exceptions properly. This is not (at all) an indication that madExcept would be causing the exception.
madshi
Site Admin
 
Posts: 9774
Joined: Sun Mar 21, 2004 5:25 pm


Return to madExcept

Who is online

Users browsing this forum: No registered users and 2 guests