Following situation: I'm developing an windows mobile application using the sdk 6. Target machine is a nautiz x7. To improve the error reporting I want to catch the structured exceptions (SEH) and do a stack backtrace to store some information for analysis.

So far I have the information where the exception was thrown (windows core.dll) and I can backtrace the return adresses thru the stack.

But what I want to know is, which instruction in my code caused the exception?

Does anyone know how to use the available exception and context information to get the appropriate function/instruction address?

Unfortunately windows mobile 6 sdk for pocketpc does not support all the helper functions to do stackwalks or mini dumps.