зеркало из https://github.com/mozilla/gecko-dev.git
71ba656859
If you happen to be unfortunate enough to be testing changes that crash xpcshell during the xpcshell self-tests, you'll be presented with error messages like: PROCESS-CRASH | test_child_assertions.js | application crashed [unknown top frame] Crash dump filename: c:\users\task_1522676338\appdata\local\temp\xpc-other-mtot6h\cfaea928-e995-4430-baf9-0066c6b91be9.dmp MINIDUMP_STACKWALK binary not found: z:\build\build\tools\breakpad\win64\minidump_stackwalk.exe and then be told that, essentially, "your test failed because it failed", which is unhelpful for figuring out what went wrong. Apparently we had MINIDUMP_STACKWALK set at one point, and then it got moved. Let's fix this situation by a) downloading minidump_stackwalk out of tooltool (our test harnesses do this already); and b) pointing MINIDUMP_STACKWALK at the correct location. With these changes, we can once again get crash stacks if xpcshell (and probably a few other things) fail their self tests. |
||
|---|---|---|
| .. | ||
| linux64 | ||
| macosx64 | ||
| win32 | ||
| win64 | ||