#2081: GHC reports internal error: stg_ap_v_ret
------------------------------+---------------------------------------------
Reporter: thorkilnaur | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 6.10.1
Component: Compiler | Version: 6.9
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: Unknown/Multiple
Os: Unknown/Multiple |
------------------------------+---------------------------------------------
Comment (by thorkilnaur):
After discussing this briefly on #ghc the other day, I tried to get back
to the version of the HEAD that had the problem, but I failed to reproduce
it. However, the two subsequent buildbot builds both have the problem
(http://darcs.haskell.org/buildbot/all/builders/tnaur%20PPC%20OSX%20head%202/builds/142
and
http://darcs.haskell.org/buildbot/all/builders/tnaur%20PPC%20OSX%20stable%202/builds/179).
And I am able to consistently reproduce the problem mentioned above with
the timeout program.
So the question is, how to proceed. Compiling with -O2 and running with
+RTS -DSs produces:
{{{
$ ./timeout 200 "echo Something" +RTS -DSs
new task (taskCount: 1)
task exiting
new task (taskCount: 1)
created thread 1, stack size = f1 words
new bound thread (1)
### NEW SCHEDULER LOOP (task: 0x600520, cap: 0x2a1178)
-->> running thread 1 ThreadRunGHC ...
created thread 2, stack size = f1 words
created thread 3, stack size = f1 words
--<< thread 1 (ThreadRunGHC) stopped: is blocked on an MVar @ 0x117f370
-->> running thread 2 ThreadRunGHC ...
--<< thread 2 (ThreadRunGHC) stopped, yielding
-->> running thread 3 ThreadRunGHC ...
thread 3 did a safe foreign call
forking!
new task (taskCount: 2)
task exiting
thread 3: re-entering RTS
timeout: internal error: stg_ap_p_ret
(GHC version 6.11.20081003 for powerpc_apple_darwin)
Please report this as a GHC bug:
http://www.haskell.org/ghc/reportabug
waking up thread 3 on cap 0
raising exception in thread 2.
raising exception in thread 1.
discarding task 6292768
created thread 4, stack size = f1 words
new bound thread (4)
### NEW SCHEDULER LOOP (task: 0x6005f0, cap: 0x2a1178)
-->> running thread 4 ThreadRunGHC ...
Something
Abort trap
$
}}}
But I am sorely in need of some hints.
Another possibility would be for some seasoned expert to get access to the
machinery and take a look.
Best regards
Thorkil
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2081#comment:10>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
