|
Your best bet, in my opinion, would be emitting different recognizeable byte sequences using
__asm { emit BYTE0; emit BYTE1; ...}
at the beginning and at the end of the function
This will however turn out to be a bit complicated for non-voids, as if you'll insert the sequence below the return instruction it'll get ignored, and if you'll insert it above the return you won't account for that...
Alternatively, if you don't need to dynamically get the value from time to time but you need it for processing after compilation of an executable, you can consider generating a mapfile for your compiled code and parse that.
Regards
|