ghc-iserv sometimes segfaults in profiled way
I have seen a few testsuite failures due to ghc-iserv
crashes like these,
--- ./profiling/should_run/T5363.run/T5363.stdout.normalised 2018-01-22 18:57:49.401773263 +0000
+++ ./profiling/should_run/T5363.run/T5363.run.stdout.normalised 2018-01-22 18:57:49.401773263 +0000
@@ -1 +1 @@
-1250030000000
+ghc-stage2: ghc-iserv terminated (-7)
*** unexpected failure for T5363(ghci-ext-prof)
Actual stdout output differs from expected:
--- ./profiling/should_run/scc001.run/scc001.stdout.normalised 2018-01-22 18:57:45.177724120 +0000
+++ ./profiling/should_run/scc001.run/scc001.run.stdout.normalised 2018-01-22 18:57:45.177724120 +0000
@@ -1,3 +1,3 @@
True
3
-'a'
+ghc-stage2: ghc-iserv terminated (-11)
*** unexpected failure for scc001(ghci-ext-prof)
Trac metadata
Trac field | Value |
---|---|
Version | 8.5 |
Type | Bug |
TypeOfFailure | OtherFailure |
Priority | normal |
Resolution | Unresolved |
Component | Profiling |
Test case | |
Differential revisions | |
BlockedBy | |
Related | |
Blocking | |
CC | |
Operating system | |
Architecture |