#10375: arm: ghci hits an illegal instruction -------------------------------------+--------------------------------- Reporter: erikd | Owner: Type: bug | Status: new Priority: normal | Milestone: 7.10.2 Component: GHCi | Version: 7.10.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: arm Type of failure: GHCi crash | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Revisions: -------------------------------------+--------------------------------- Comment (by erikd): Managed to run `ghc-stage2 --interactive` in one terminal and the attach GDB to it in another using `ghc -tui -p <pid>`. I can then manually enter the two lines of test case code and have it segfault. The GDB backtrace is a little odd (even by haskell program standards): {{{ Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb14ff460 (LWP 19914)] Cannot access memory at address 0xb88849d4 (gdb) bt #0 0xb88849d4 in ?? () #1 0x70000000 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) }}} but that address `0xb88849d4` being in both the "Cannot access memory at" message and the stack might point to stack corruption while the `0x70000000` address on the stack is *very* suspicious. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/10375#comment:11 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler