Open
Bug 1798516
Opened 2 years ago
Updated 2 years ago
Remove libdisasm?
Categories
(Toolkit :: Crash Reporting, enhancement)
Toolkit
Crash Reporting
Tracking
()
NEW
People
(Reporter: tjr, Unassigned)
Details
It seems like all of the libdisasm code is only used by the exploitability check, which we disable. I don't know much about how we build/vendor breakpad but if it's simple, we might be able to rip out all of libdisasm and save some space.
Comment 1•2 years ago
|
||
We still build the breakpad processor as part of the minidump-analyzer, to remove the libdisasm code we'd have to patch out this code, then adjust the moz.build
file to not include the exploitability and libdisasm code and finally add libdisasm to the list of code we remove in the breakpad update script.
This should make the minidump-analyzer smaller (and thus the installer) and shorten the build a bit. We intend to remove breakpad in its entirety but this might still be worth doing in the meantime.
You need to log in
before you can comment on or make changes to this bug.
Description
•