Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!mit-eddie!uw-beaver!sumax!quick!thebes!camco!bill
From: bill@camco.Celestial.COM (Bill Campbell)
Newsgroups: comp.lang.perl
Subject: Re: problem with "out of memory" in perl debugger
Keywords: perl, debugger, bug, out of memory
Message-ID: <553@camco.Celestial.COM>
Date: 14 Dec 90 18:30:49 GMT
References: <40012@genrad.UUCP> <278@carssdf.UUCP>
Organization: Celestial Software, Mercer Island, WA
Lines: 27

In <278@carssdf.UUCP> usenet@carssdf.UUCP (John Watson) writes:

	In article <40012@genrad.UUCP>, rep@genrad.com (Pete Peterson) writes:
	> On the vax, perl -d ANYTHING gives segmentation fault core dump.
	> Has anybody seen and fixed this problem?

	A problem on SCO Xenix similar to this was corrected by changing the
	compile options to include -Zp2,  That means pack all structures on
	short word (2 byte) boundaries.  The ARG structure has a pointer
	followed by three shorts and this seems to be related to the problem.
	When the problem hits, "afake" asks for 100 + M Byte of memory.

	On the Xenix System, that change also requires you to fix the "stat.h"
	include module, or just accept a couple of errors from the make test,
	of io.fs and op.stat.   A #pragma pack(4) and ...pack() do
	the trick.

	John Watson   ...!rutgers!carssdf!usenet

Is there an equivalent when compiling with gcc?

The current options are '-fpcc-struct-return -UM_I386 -O'

-- 
INTERNET:  bill@Celestial.COM   Bill Campbell; Celestial Software
UUCP:   ...!thebes!camco!bill   6641 East Mercer Way
             uunet!camco!bill   Mercer Island, WA 98040; (206) 947-5591