From vannoord@let.rug.nl  Sun Feb 13 14:47:01 2000
Received: from froh.let.rug.nl (vannoord@froh.let.rug.nl [129.125.8.25])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id OAA14507
	for <prolog@swi.psy.uva.nl>; Sun, 13 Feb 2000 14:47:00 +0100 (MET)
Received: (from vannoord@localhost)
	by froh.let.rug.nl (8.9.3/8.9.3) id OAA10124
	for prolog@swi.psy.uva.nl; Sun, 13 Feb 2000 14:47:29 +0100 (MET)
From: "Noord G.J.M. van" <G.J.M.van.Noord@let.rug.nl>
Message-Id: <200002131347.OAA10124@froh.let.rug.nl>
Subject: 3.3 on Alpha/Linux anyone?
To: prolog@swi.psy.uva.nl
Date: Sun, 13 Feb 2000 14:47:28 +0100 (MET)
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Has anyone successfully installed swi 3.3 on Alpha/Linux? I'm getting
the following error on a SuSe 6.3 based system (glibc 2.1):

./pl -O -o pl.prc -b ../boot/init.pl
Loading boot file ...
Loading Prolog startup files
%  messages boot compiled into $messages 0.02 sec, 86,680 bytes
%  toplevel boot compiled into $toplevel 0.01 sec, 52,880 bytes
%  listing boot compiled into $listing 0.01 sec, 26,600 bytes
%  make boot compiled into $make 0.00 sec, 5,168 bytes
%  sort boot compiled into $sort 0.00 sec, 14,080 bytes
%  bags boot compiled into $bags 0.00 sec, 5,496 bytes
[PROLOG SYSTEM ERROR:
        Recursively received fatal signal 11

PROLOG STACK:
  (37) system:$load_files([apply, list, writef, history, dwim, parms, autoload,
qlf, rc, user:topvars], system, [])
    <Alien goal>
^ (29) system:with_mutex($load, $load_files([syspred, messages, toplevel, listin
g, make, sort, bags, apply, list, writef, history, dwim, parms, autoload, qlf, r
c, user:topvars], system, []))                                               
... etc

gdb says:

Program received signal SIGSEGV, Segmentation fault.
0x120015300 in PL_unregister_atom ()
(gdb) where
#0  0x120015300 in PL_unregister_atom ()
#1  0x12005f9dc in unregisterAtomsRecord ()
#2  0x12005f9dc in unregisterAtomsRecord ()
warning: Hit beginning of text section without finding
warning: enclosing function for address 0x262
This warning occurs if you are debugging a function without any symbols
(for example, in a stripped executable).  In that case, you may wish to
increase the size of the search with the `set heuristic-fence-post' command.

Otherwise, you told GDB there was a function where there isn't one, or
(more likely) you have encountered a bug in GDB.                               


