Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!hollie.rdg.dec.com!forty2.enet.dec.com!moore
From: moore@forty2.enet.dec.com (Paul Moore)
Newsgroups: comp.unix.sysv386
Subject: malloc() problem on sysv386
Message-ID: <1991May23.094026.18969@hollie.rdg.dec.com>
Date: 23 May 91 10:33:16 GMT
Sender: news@hollie.rdg.dec.com (Mr News)
Organization: Digital Equipment Corporation
Lines: 16

I've recently had this error occuring when malloc is called running an
application on ISC SVR3.2 (observed from the sdb debugger):

   memory fault (11) (sig 11)

The man page for signal(3) indicates that this is a segmentation violation. 

The problem only occurs when malloc() had been previously called in the code
execution path; it doesn't appear when this code path isn't executed.

The problem doesn't appear at all when I run the very same application on
Ultrix.

Any ideas, anyone?

- Paul