I am using MSVC 6.0 to call a macro in the Win32API and I’m getting an access violation. I know that the pointers I’m passing to the macro contain valid addresses, though they’re evidently not pointing to the correct data.
The macro accepts multiple pointers, and I’m not sure which pointer is erroneous, so I’d like to use MSVC’s debugger to ‘step into’ the macro to see exactly where the problem is. When I’ve tried thus far, the debugger just throws the access violation error.
Is it possible to ‘step into’ a macro using MSVC 6.0’s debugger? If not, is there anyway for me to check what the macro expands to, so I can get a better idea of what I’m not doing correctly?
If you really need to trace the macro code, the only way would be to find the definition of the macro, manually “instantiate” the macro code (substituting the parameters) in place where it is “called”, and then trace it in the debugger as ordinary code.
Alternative variant would be to step through the disassembly, if your skill level is sufficient to back-associate the disassembled code with the original macro code.