Register the WER runtime exception module at runtime
Categories
(Toolkit :: Crash Reporting, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox89 | --- | fixed |
People
(Reporter: gsvelto, Assigned: gsvelto)
References
Details
Attachments
(1 file)
For a WER runtime exception module to work we also need to register it at runtime in Gecko using the WerRegisterRuntimeExceptionModule() function. Note that the function does not check if the passed path exists and does not return an error if the module wasn't found. We need to make sure that it's where it's supposed to be and properly stored in the registry.
It's possible to pass a raw pointer to a context that will be passed to the callbacks though it's unclear what data can be passed with it.
|
Assignee | |
Updated•3 years ago
|
|
|
Assignee | |
Comment 1•3 years ago
|
||
Note that we'll have to figure out what's the best way to handle browser / child process crashes. We'll probably need to call WerRegisterRuntimeExceptionModule() with a different context in child processes so that the hooks can tell the different crashes apart. I don't think that we'll need separate modules for the different processes though. Note that WerRegisterAdditionalProcess() cannot be used for this purpose, its role seems to be akin to our paired minidump generation: it can be used to add an additional minidump when the registering process crashes.
|
|
Assignee | |
Comment 2•3 years ago
|
||
Depends on D101708
|
||
Updated•3 years ago
|
Pushed by gsvelto@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f7de5372675b Register the Windows Error Reporting exception module so that it can intercept main process crashes r=dmajor
|
||
Comment 4•3 years ago
|
||
| bugherder | ||
Description
•