[Msys2-users] Debugging undeterministic segfaults

David Macek david.macek.0 at gmail.com
Wed Nov 5 10:36:47 UTC 2014

Sorry for the large amount of messages.

On 5. 11. 2014 8:01, David Macek wrote:
> I'm running validate to double check (detected 4 CPUs).

I got the validate results:

> Unexpected results from:
> TEST="linker_unload listCommand002 T5681 T5486 T7571 ghcpkg05 T3924 T7702 plugins01 T6106 ghci038 T8172 ghci032 T5975a T5975b ghci058 T3064 T3307 environment001 T876 T3738 T4830 T5205 T7436 lazy-bs-alloc T1407 rdynamic T7037 T5423 T8124 T5435_dyn_asm prog012 prog013 prog001 prog002 prog003 T4006"
> OVERALL SUMMARY for test run started at 11/05/14 09:04:01 Central Europe Standard Time
>  1:01:50 spent to go through
>     4095 total tests, which gave rise to
>    14911 test cases, of which
>    11167 were skipped
>       58 had missing libraries
>     3578 expected passes
>       71 expected failures
>        1 caused framework failures
>        1 unexpected passes
>       36 unexpected failures
> Unexpected passes:
>    rts  linker_unload (normal)
> Unexpected failures:
>    ../../libraries/base/tests     T4006 [bad stdout] (normal)
>    ../../libraries/base/tests/IO  T3307 [bad exit code] (normal)
>    ../../libraries/base/tests/IO  environment001 [bad stdout] (normal)
>    cabal                          ghcpkg05 [bad stderr] (normal)
>    callarity/perf                 T3924 [stat too good] (normal)
>    ghci.debugger/scripts          listCommand002 [bad stderr] (ghci)
>    ghci/linking                   T1407 [bad stderr] (ghci)
>    ghci/prog001                   prog001 [bad stderr] (ghci)
>    ghci/prog002                   prog002 [bad stderr] (ghci)
>    ghci/prog003                   prog003 [bad exit code] (ghci)
>    ghci/prog012                   prog012 [bad stderr] (ghci)
>    ghci/prog013                   prog013 [bad stderr] (ghci)
>    ghci/scripts                   T5975a [bad stderr] (ghci)
>    ghci/scripts                   T5975b [bad stderr] (ghci)
>    ghci/scripts                   T6106 [bad stderr] (ghci)
>    ghci/scripts                   T8172 [bad stdout] (ghci)
>    ghci/scripts                   ghci032 [bad stderr] (ghci)
>    ghci/scripts                   ghci038 [bad stderr] (ghci)
>    ghci/scripts                   ghci058 [bad stderr] (ghci)
>    llvm/should_compile            T5486 [stderr mismatch] (optllvm)
>    llvm/should_compile            T5681 [stderr mismatch] (optllvm)
>    llvm/should_compile            T7571 [stderr mismatch] (optllvm)
>    perf/compiler                  T3064 [stat not good enough] (normal)
>    perf/should_run                T3738 [stat too good] (normal)
>    perf/should_run                T4830 [stat too good] (normal)
>    perf/should_run                T5205 [stat too good] (normal)
>    perf/should_run                T7436 [stat too good] (normal)
>    perf/should_run                T876 [stat not good enough] (normal)
>    perf/should_run                lazy-bs-alloc [stat not good enough] (normal)
>    plugins                        plugins01 [bad stderr] (normal)
>    rts                            T5423 [bad stdout] (normal)
>    rts                            T5435_dyn_asm [bad stdout] (normal)
>    rts                            T7037 [bad stdout] (normal)
>    rts                            T8124 [exit code non-0] (threaded1)
>    rts                            rdynamic [bad exit code] (normal)
>    simplCore/should_compile       T7702 [stderr mismatch] (normal)

I assume that means the build itself had no errors.

David Macek

More information about the ghc-devs mailing list