#14705 closed bug (fixed)
ghc-iserv sometimes segfaults in profiled way
Reported by: | bgamari | Owned by: | simonmar |
---|---|---|---|
Priority: | highest | Milestone: | 8.4.2 |
Component: | Profiling | Version: | 8.5 |
Keywords: | Cc: | ||
Operating System: | Unknown/Multiple | Architecture: | Unknown/Multiple |
Type of failure: | Runtime crash | Test Case: | |
Blocked By: | Blocking: | ||
Related Tickets: | Differential Rev(s): | Phab:D4437 | |
Wiki Page: |
Description
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)
Change History (8)
comment:3 Changed 12 months ago by
Differential Rev(s): | → Phab:D4437 |
---|---|
Milestone: | → 8.4.1 |
Owner: | set to simonmar |
Priority: | normal → highest |
comment:4 Changed 12 months ago by
FYI @bgamari, in the future we need to consider these things to be release-blocking. Running the interpreter with profiling is supposed to work (and we rely on it heavily at FB), but unfortunately we only have a few tests for it. Basically what should have happened here is that CI should have picked up the failing tests on the diff that broke it - so this is an argument for keeping profiling turned on in our new CircleCI setup.
comment:7 Changed 12 months ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Merged for 8.4.1 as well.
comment:8 Changed 11 months ago by
Milestone: | 8.4.1 → 8.4.2 |
---|
Unfortunately due to an oversight in the release preparation process, the fix for this issue was not included in the 8.4.1 release. It will, however, be present in the soon-to-arrive 8.4.2.
Looking at
scc001
, it looks like we get into trouble in the interpreter,For future reference, getting here involved,