diff options
| author | bors-servo <lbergstrom+bors@mozilla.com> | 2019-12-12 16:23:40 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-12-12 16:23:40 -0500 |
| commit | a5c368fd0115527aaaa555641d292be43258a6ef (patch) | |
| tree | 06a71c4c53e4237f440459a4ec6b3af82b3d159a /components/script/dom/webidls/DOMException.webidl | |
| parent | 9f1d46949053ae48df15e4030506df111e3d34ae (diff) | |
| parent | c27b4e259a0a20044812d8f84fc8b9289d1f12f8 (diff) | |
| download | servo-a5c368fd0115527aaaa555641d292be43258a6ef.tar.gz servo-a5c368fd0115527aaaa555641d292be43258a6ef.zip | |
Auto merge of #25248 - MeFisto94:fix-linux-crash-libbacktrack, r=jdm
Workaround for #24984 - Solve crashes when panicking / Hang Monitoring by using cargo's patch mechanism to work around a bug in libbacktrace
Temporarly patch backtrace-rs
---
libbacktrace contains an error leading to invalid pointers when trying to backtrace a stacktrace.
These invalid pointers led to a crash, whenever a panic or Hang Monitoring happened (which is where the stack is captured).
Since fixing the issue properly at gcc will require some time, I've created a small and patched version of backtrace-rs, which will be used as patch here.
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
- [X] These changes fix #24984
- [X] These changes do not require tests because they fix a native crash which is a) really obvious and b) shouldn't be a regular case.
Diffstat (limited to 'components/script/dom/webidls/DOMException.webidl')
0 files changed, 0 insertions, 0 deletions