How can I detect which callback from an unmanaged dll causes a protected memory exception?
Posted
by Kristian Hebert
on Stack Overflow
See other posts from Stack Overflow
or by Kristian Hebert
Published on 2010-03-26T10:15:24Z
Indexed on
2010/03/26
12:33 UTC
Read the original article
Hit count: 385
I get a protected memory exception, but how can I know which call caused it, and why the callback function has moved? All the calls to unmanaged code are done in the same class as the callback functions, so I suppose that the addresses should not change, or am I totally wrong here?
© Stack Overflow or respective owner