Critical Description
When writing to memory sections shared by all processes (for example, the code section in a dll like kernel32.dll) the modifications are visible in all processes.
Discovered / documented in CORE-6391
Application to confirm behavior in CORE-10153 (although every process going down because of breakpoints also is a clear indication of a problem).
Steps to reproduce (duplicated from CORE-6391):
- Load any process in depends (Dependency walker).
- Start profiling. (At this point, depends sets a breakpoint in all dll's loaded by the target process).
- Every process now has breakpoints in all dll's loaded by depends target.
Update:
This is not always triggered.
Change memory protection from PAGE_EXECUTE_READ to PAGE_EXECUTE_WRITECOPY --> Problem.
Change memory protection from PAGE_EXECUTE_READ to PAGE_EXECUTE_READWRITE to PAGE_EXECUTE_WRITECOPY --> Everything appears to be fine.
Attachments
Issue Links
- blocks
-
CORE-6391 csrss: Crash in Dependency Walker when profiling with DllMain calls for process attach/detach logging
-
- Resolved
-
-
-
- Resolved
-
- is blocked by
-
-
- Resolved
-
-
CORE-8541 Implement copy-on-write support in ARM3 page fault handler
-
- Resolved
-
- relates to
-
CORE-10153 PATCH: memwatch
-
- Resolved
-