Bugs item #1199364, was opened at 2005-05-10 20:21
Message generated for change (Comment added) made by simonmar
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=1199364&group_id=8032

Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: internal error: scavenge_one: strange object 68, amd64

Initial Comment:
With
  ghc-6.4.20050506-src.tar.bz2  or ghc 6.4
  Fedora Core 3 (current updates) (gcc 3.4.3 glibc 2.3.5)
  amd64
  Existing ghc 6.4 in /usr/bin from Fedora Haskell
Project rpm.
  pugs r2943

I built ghc-6.4.20050506-src by doing:
  ./configure
  make
  make
  make install

But ghc-6.4 behaves similarly.

You can build pugs by doing:
  svn co http://svn.openfoundry.org/pugs/ -r 2943
  cd pugs
  perl Makefile.PL
  make unoptimized

To generate error,
  ./pugs

Error:
 [...]
  Welcome to Pugs -- Perl6 User's Golfing System
  Type :h for help
  
  pugs: internal error: scavenge_one: strange object 68
      Please report this as a bug to
glasgow-haskell-bugs@haskell.org,
      or http://www.sourceforge.net/projects/ghc/

Notes:
  Using /usr/bin/ghc (ghc-6.4) yields a similar error.
  ./pugs +RTS -A200M -RTS  delays the error.

Mitchell Charity
mncI02eyA  zap  vendian zot org


----------------------------------------------------------------------

>Comment By: Simon Marlow (simonmar)
Date: 2005-05-11 10:49

Message:
Logged In: YES 
user_id=48280

Thanks, I've now fixed this.

STM looks pretty broken on amd64 because of this bug.  6.4.1
should be better, or build from a new source snapshot
(tomorrow or later).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=1199364&group_id=8032
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to