On 08/01/2013 16:15, Eero Tamminen wrote:
Any comments on how one can debug what happens inside OS during OS call or what data could get overwritten inside OS?
I had similar problem when debugging the abominable XaAES bug in ob_fix_shortcuts(). I added traces in XaAES itself to see if the bug had already happened, or not. Then narrow the traces to determine the location of the bug more precisely.
Another approach is to put some kind of breakpoint in the code (infinite loops, etc.) and examine the memory with an external debugger. Ideally a "data breakpoint" tool would be perfect.
Good luck. -- Vincent Rivière