russ@wpg.UUCP (Russell Lawrence) (01/13/89)
I'm working on a small unify application that will require me to use
the unify selsort() function for the first time.
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.
Has anyone else encountered selsort problems? Any suggestions
would be *greatly* appreciated.
--
Russell Lawrence, WP Group, New Orleans (504) 456-0001
{uunet,killer}!wpg!russscotth@harlie.SGI.COM (Scott Henry) (01/14/89)
From article <1074@wpg.UUCP>, by russ@wpg.UUCP (Russell Lawrence): > > I'm working on a small unify application that will require me to use > the unify selsort() function for the first time. > > 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. Having just experienced the same problem... The manual entry for selsort() is wrong. It shows the prototype as (I can't use italics): selsort(tnum,fldtbl,srtfunc) int tnum, *fldtbl; int (*functbl[])() = {selfunc,confunc,srtfunc,tagfunc}; the argument line should read: selsort(tnum,fldtbl,functbl) > Has anyone else encountered selsort problems? Any suggestions > would be *greatly* appreciated. I am still having problems with my application, but I _think_ they are now not in selsort(). Good luck. > -- > Russell Lawrence, WP Group, New Orleans (504) 456-0001 > {uunet,killer}!wpg!russ ## scott henry <scotth@sgi.com> ## Silicon Graphics, Inc. -- Scott Henry
scotth@harlie.SGI.COM (Scott Henry) (01/14/89)
From article <24897@sgi.SGI.COM>, by scotth@harlie.SGI.COM (Scott Henry):
> From article <1074@wpg.UUCP>, by russ@wpg.UUCP (Russell Lawrence):
Err, I am using Unify 4.0 (I forgot to look at the version). I suppose
the same bug might be there also.
## scott henry <scotth@sgi.com>
## Silicon Graphics, Inc.
--
Scott Henryallbery@ncoast.UUCP (Brandon S. Allbery) (01/20/89)
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