Path: utzoo!attcan!uunet!lll-winken!ames!xanth!nic.MR.NET!hal!ncoast!allbery
From: allbery@ncoast.UUCP (Brandon S. Allbery)
Newsgroups: comp.databases
Subject: Re: unify 3.2 selsort() problems
Message-ID: <13349@ncoast.UUCP>
Date: 20 Jan 89 04:55:26 GMT
References: <1074@wpg.UUCP>
Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery)
Followup-To: comp.databases
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 22

As quoted from <1074@wpg.UUCP> by russ@wpg.UUCP (Russell Lawrence):
+---------------
| I've invoked selsort() as outlined in the unify manuals, but the
| resulting program crashes and reports "memory error".  I can't
| ascertain precisely where the problem lies because unify is
| apparently trapping signals and preventing the system from creating
| a core file.
+---------------

I've used selsort() many times -- 3.1, 3.2, 4.0 -- without problems.
However, at least one machine's version of 4.0 has a problem with the
related function unisort() (it can be called exactly once, other times it
returns nothing).  Your machine's version of selsort() may have a problem of
some kind; which OS, machine, etc.?  (Tell Unify, not me.  I'm just a
consultant/programmer.)

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc    allbery@ncoast.org (soon)
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery@hal.cwru.edu
      Send comp.sources.misc submissions to comp-sources-misc@<backbone>
NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser