Changes between Initial Version and Version 1 of Ticket #96, comment 8


Ignore:
Timestamp:
Jun 2, 2011, 1:59:44 PM (8 years ago)
Author:
dmik
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #96, comment 8

    initial v1  
    1 I got the above problem fixed, finally, see r21633. Even though I couldn't find the exact code that trashes fs:[0], tests show that the problem has gone. I could use SmartSVN 6.6 for committing r21633 :) And for browsing other complex projects like Qt which trigger a lot of exceptions caught in !__try/!__except.
     1I got the above problem fixed, finally, see r 21633 (in Odin SVN). Even though I couldn't find the exact code that trashes fs:[0], tests show that the problem has gone. I could use SmartSVN 6.6 for committing r 21633 :) And for browsing other complex projects like Qt which trigger a lot of exceptions caught in !__try/!__except.
    22
    33My assumption about killing the contents of fs:[0] is that in some rare cases the OS/2 kernel doesn't load 0x150b (the thread data segment used in OS/2) to FS when the OS/2 system exception is generated, and therefore it writes the new exception handler data (used for some internal processing) to the Win32 thread data segment (which we abuse FS for when working in Win32 compatibility mode). I couldn't easily prove that but as long as it works now I don't see the need in spending more time on that.