Changes between Initial Version and Version 1 of Ticket #96, comment 5
- Timestamp:
- May 25, 2011, 5:25:41 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #96, comment 5
initial v1 1 I guess I found the cause for the second crash. Java uses the __try exception handler's address stored in fs:[0] as a base for a very fast access to a the Thread object (stored on the same stack some bytes away).1 I guess I found the cause for the second crash. Java uses the !__try exception handler's address stored in fs:[0] as a base for a very fast access to a the Thread object (stored on the same stack some bytes away). 2 2 3 3 However, under some circumstances, while being executed in JVM-generated code, fs:[0] gets zeroed. This breaks both the exception handling and the Thread object access. I somehow need to find out who's zeroing it.