Spurious segfault on powerpc

[japaric]

From #155

test mulodi4 ... Invalid data memory access: 0xf6fff46c

NIP f66a59b4   LR f669cc3c CTR f66a4724 XER 00000000 CPU#1

MSR 00006040 HID0 00000000  HF 00006000 idx 0

TB 00000133 574871746592

GPR00 00000000f669ca80 00000000f657eb30 00000000f65868c0 00000000f6fff100

GPR04 00000000f6fff190 000000006ff64640 0000000000000024 0000000000000024

GPR08 00000000f6fff194 00000000f6fff448 0000000000000348 0000000000000000

GPR12 0000000028428824 00000000f6fff0f4 00000000f6ecc5bc 00000000f66cd018

GPR16 000000006ff8b2a8 00000000f657f450 00000000f6589488 00000000f6ecacdc

GPR20 00000000f6f3fab8 000000006ff8d2f4 0000000000000000 0000000000000000

GPR24 00000000f6ecace0 00000000f66862a0 00000000f66cc308 00000000f6fff190

GPR28 0000000000130190 00000000f6ecf000 00000000f66ccff4 00000000f66cd910

CR 22428828  [ E  E  G  E  L  L  E  L  ]             RES ffffffff

FPR00 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR04 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR08 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR20 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR24 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR28 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPSCR 00000000

Invalid segfault errno (42000000)

NIP f66a59b4   LR f669cc3c CTR f66a4724 XER 00000000 CPU#1

MSR 00006040 HID0 00000000  HF 00006000 idx 0

TB 00000133 574872603121

GPR00 00000000f669ca80 00000000f657eb30 00000000f65868c0 00000000f6fff100

GPR04 00000000f6fff190 000000006ff64640 0000000000000024 0000000000000024

GPR08 00000000f6fff194 00000000f6fff448 0000000000000348 0000000000000000

GPR12 0000000028428824 00000000f6fff0f4 00000000f6ecc5bc 00000000f66cd018

GPR16 000000006ff8b2a8 00000000f657f450 00000000f6589488 00000000f6ecacdc

GPR20 00000000f6f3fab8 000000006ff8d2f4 0000000000000000 0000000000000000

GPR24 00000000f6ecace0 00000000f66862a0 00000000f66cc308 00000000f6fff190

GPR28 0000000000130190 00000000f6ecf000 00000000f66ccff4 00000000f66cd910

CR 22428828  [ E  E  G  E  L  L  E  L  ]             RES ffffffff

FPR00 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR04 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR08 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR20 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR24 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPR28 0000000000000000 0000000000000000 0000000000000000 0000000000000000

FPSCR 00000000

thread '<unnamed>' panicked at 'assertion failed: c.borrow().is_none()', /checkout/src/libstd/sys_common/thread_info.rs:51

note: Run with `RUST_BACKTRACE=1` for a backtrace.

fatal runtime error: failed to initiate panic, error 4134036808

qemu: uncaught target signal 6 (Aborted) - core dumped

error: process didn't exit successfully: `/target/powerpc-unknown-linux-gnu/debug/deps/mulodi4-67cf1fbdd87f7066` (signal: 6, SIGABRT: process abort signal)

I have seen this target spuriously segfault while running tests on other project so this may be some QEMU bug.

[AaronKutch]

Has this problem been seen recently?

[tgross35]

We have bumped qemu a few times since then - some ppc crashes seem to have gotten fixed in the latest version. Not sure about the exact problem listed here, but I don't think there is any point in keeping this open if they haven't been seen in a while.