Open
Bug 1874886
Opened 1 year ago
Updated 4 months ago
Windows Error Reporting does not work for child processes when Win32k lockdown is enabled
Categories
(Toolkit :: Crash Reporting, enhancement)
Toolkit
Crash Reporting
Tracking
()
NEW
People
(Reporter: gsvelto, Unassigned)
References
(Depends on 1 open bug)
Details
As per title, the WER runtime exception module currently uses win32k calls and fails to work when the crashed process uses win32 lockdown. To fix this we need to remove the affected calls and change how the module notifies the main process:
- The runtime exception module will only identify what kind of process caused the crash, write the exception information to a global shared mapping and pass it on to the main process
- The responsibility for writing the minidump and fetching the crash annotations should move entirely to the main process
- The main process is responsible for killing the crashed process once the crash report has been written, however we can do the same in the runtime exception module just to be extra sure
All the communication between the runtime exception module and the main process will use handles instead of PIDs, to prevent issues related to PID reuse.
Updated•6 months ago
|
Summary: Windows Error Reporting does not work for child processes when Win32 lockdown is enabled → Windows Error Reporting does not work for child processes when Win32k lockdown is enabled
Updated•6 months ago
|
Depends on: oop-crashreporter
You need to log in
before you can comment on or make changes to this bug.
Description
•