How can I detect which callback from an unmanaged dll causes a protected memory exception?
- by Kristian Hebert
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?