Hi folks,
We have been using a custom built Visual Studio 32 bit expression evaluator addin since VC6 (EEAddin) for a large native 32 bit C program. We are now using VS 2010 SP1 and have ported our 32 bit application to a native 64 bit application.
Ideally, I want to use this single EEAddin to debug 32 bit cross compiled and 64 bit versions of our application so that we can look at various complex C structures in memory.
I have moved our EEAddin code to use the memory function ReadDebuggeeMemoryEx() but because the EEAdin DLL we have is compiled as a 32bit DLL (because devenv.exe is a 32 bit application even on Win64) I'm wondering how I might know the size of various structures and the offset of various members within that chunk of memory.
At the moment our 32 bit EEAddin code simply uses the same header files as the debugged application so that we may simply use the same structure definitions when creating the output strings but the problem is in the case of a 64 bit application these memory locations are completely different. We can't simply use sizeof() and member pointers into structures.
We did find this article about solving the problem:
http://www.myopictopics.com/?m=201106
but do we really need to go to these lengths?
Does anyone else know of any tricks or support for writing native addins for native 64 bit applications?
Cheers
John Kamp
John Kamp