Hello , yes, i found this famous "-c" bug! the humor of situation is what easiest way to got this bug is to run ghc itself! :) it seems that noone except me tried this ever. i just found that any large enough module raises this error!!! that, for example, results of compiling Data.Map module:
ghc Map.hs -cpp +RTS -c ghc.EXE: internal error: update_fwd: unknown/strange object 39004 Please report this as a bug to glasgow-haskell-bugs@haskell.org, or http://www.sourceforge.net/projects/ghc/
ghc 6.4.1/mingw32. the error is absolutely reproducible, so at least now we had case, even lot of cases :) or you wanna a smaller program? :) -- Best regards, Bulat mailto:bulatz@HotPOP.com
Bulat Ziganshin wrote:
Hello ,
yes, i found this famous "-c" bug! the humor of situation is what easiest way to got this bug is to run ghc itself! :) it seems that noone except me tried this ever. i just found that any large enough module raises this error!!! that, for example, results of compiling Data.Map module:
ghc Map.hs -cpp +RTS -c
ghc.EXE: internal error: update_fwd: unknown/strange object 39004 Please report this as a bug to glasgow-haskell-bugs@haskell.org, or http://www.sourceforge.net/projects/ghc/
ghc 6.4.1/mingw32. the error is absolutely reproducible, so at least now we had case, even lot of cases :)
or you wanna a smaller program? :)
I think this may be a different bug - I can reproduce it, but not with the current STABLE branch. It is probably the freeze/thaw bug that was fixed after 6.4.1. However, I've still seen strange crashes in STABLE when using +RTS -c. We build stage 3 of the nightly build with +RTS -c every night, and right now we aren't getting any crashes, but a few weeks ago we were. When I looked into it, I couldn't get a deterministically repeatable crash - every tiny change made the crash go away. Cheers, Simon
Hello Simon, Monday, February 06, 2006, 5:20:17 PM, you wrote: SM> I think this may be a different bug - I can reproduce it, but not with SM> the current STABLE branch. It is probably the freeze/thaw bug that was SM> fixed after 6.4.1. SM> However, I've still seen strange crashes in STABLE when using +RTS -c. SM> We build stage 3 of the nightly build with +RTS -c every night, and SM> right now we aren't getting any crashes, but a few weeks ago we were. SM> When I looked into it, I couldn't get a deterministically repeatable SM> crash - every tiny change made the crash go away. i think that my problems is because of this bug, if it is far more frequent. at least i will be glad if ghc and my program will be no more crashed. one problem why i postpone downloading of current stable compiler is the http://hackage.haskell.org/trac/ghc/ticket/637 bug. can you please try to fix it? -- Best regards, Bulat mailto:bulatz@HotPOP.com
Bulat Ziganshin wrote:
Hello Simon,
Monday, February 06, 2006, 5:20:17 PM, you wrote:
SM> I think this may be a different bug - I can reproduce it, but not with SM> the current STABLE branch. It is probably the freeze/thaw bug that was SM> fixed after 6.4.1.
SM> However, I've still seen strange crashes in STABLE when using +RTS -c. SM> We build stage 3 of the nightly build with +RTS -c every night, and SM> right now we aren't getting any crashes, but a few weeks ago we were. SM> When I looked into it, I couldn't get a deterministically repeatable SM> crash - every tiny change made the crash go away.
i think that my problems is because of this bug, if it is far more frequent. at least i will be glad if ghc and my program will be no more crashed. one problem why i postpone downloading of current stable compiler is the http://hackage.haskell.org/trac/ghc/ticket/637 bug.
I suggest you just download STABLE and try to use it. The bug occurs much less frequently with the latest STABLE. If you can reproduce it, we really need to know about it.
can you please try to fix it?
I'm doing my best :-/ Cheers, Simon
participants (2)
-
Bulat Ziganshin -
Simon Marlow