Bug 622120 – dev-lisp/gcl-2.6.12 : Error: ERROR "Caught fatal error [memory may be damaged]"

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Toralf Förster 2017-06-18 14:32:41 UTC]

>
Error: ERROR "Caught fatal error [memory may be damaged]"
Signalled by SYSTEM:SAVE-SYSTEM.
ERROR "Caught fatal error [memory may be damaged]"


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

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.0-desktop_20170610-230638

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

gcc-config -l:
 [1] x86_64-pc-linux-gnu-6.3.0 *

Available Python interpreters, in order of preference:
  [1]   python3.4
  [2]   python3.6 (fallback)
  [3]   python2.7 (fallback)
  [4]   jython2.7 (fallback)
Available Ruby profiles:
  [1]   ruby21 (with Rubygems)
  [2]   ruby22 (with Rubygems) *
java-config:
The following VMs are available for generation-2:
*)	IcedTea JDK 3.4.0 [icedtea-bin-8]
Available Java Virtual Machines:
  [1]   icedtea-bin-8  system-vm

[Comment 1 Toralf Förster 2017-06-18 14:32:44 UTC]

Created attachment 477000 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2017-06-18 14:32:47 UTC]

Created attachment 477002 [details]
dev-lisp:gcl-2.6.12:20170617-110103.log

[Comment 3 Toralf Förster 2017-06-18 14:32:50 UTC]

Created attachment 477004 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2017-06-18 14:32:54 UTC]

Created attachment 477006 [details]
environment

[Comment 5 Toralf Förster 2017-06-18 14:32:57 UTC]

Created attachment 477008 [details]
etc.portage.tbz2

[Comment 6 Toralf Förster 2017-06-18 14:33:00 UTC]

Created attachment 477010 [details]
logs.tbz2

[Comment 7 Toralf Förster 2017-06-18 14:33:03 UTC]

Created attachment 477012 [details]
temp.tbz2

[Comment 8 Petr Zima 2020-04-02 19:22:12 UTC]

Check bug #683256, I have uploaded ebuild for gcl-2.6.13_pre90 which works for me.