Benjamin Thaut Wrote: > I'm currently implementing a stack backtrace for D 2.0 which provides > additional information for D Errors and Exceptions through the runtime trace > handler. It is already working for exceptions and errors, but for a access > violation the trace handler is not called. As I'm currently writing the > windows version of the backtracer (linux version will follow) I tried to use > the UnhandeledExceptionFilter from the win api, but it is not being called > when a access violation happens, so it seems that the D 2.0 implementation > does handle the error in some way. Is there a other error handler that is > being called on a access violation or is there no possibility to provide a > backtrace for a access violation yet?
Errors that originate from the Windows SEH are constructed a bit differently. I'll have to make sure this is done in a way that triggers the trace handler.
