Mail Archives: djgpp/2009/05/20/19:15:07

X-Authentication-Warning: mail set sender to djgpp-bounces using -f
NNTP-Posting-Date: Wed, 20 May 2009 18:00:36 -0500
From: "Charles Sandmann" <cwsdpmi AT earthlink DOT net>
Newsgroups: comp.os.msdos.djgpp
References: <0KJY00585R208H10 AT mta5 DOT srv DOT hcvlny DOT cv DOT net>
Subject: Re: Increasing area for variable storage
Date: Wed, 20 May 2009 18:00:35 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Response
Message-ID: <>
Lines: 31
X-Trace: sv3-uUDpKFMHkOSKrHXBMem0CrhTewpgmBePi1W+UdsToZ72YECmjOSQqn+xzwkeaSdRAfjaP5dhUf68/+E!mESswfOJbhpJHitF1xQ89xuU/k9mjVOTOLjQVp02tSyMFQ/IGPh6A/6mQFZnfmvQ7tA5+8YOqUT/!mw1jud8QT4OgR8em7X0mNAfNdKZ1Abs=
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.39
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

"Ethan Rosenberg" <ethros AT earthlink DOT net> wrote in message 
news:0KJY00585R208H10 AT mta5 DOT srv DOT hcvlny DOT cv DOT net...
> Dear List -
> Thank you for all your help in the past.
> I am running DOS 7.1 [the DOS that underlies Windows98].  The computer 
> does NOT have Windows installed on it.
> I have a program that had a size of 228,038 bytes and ran perfectly in the 
> past.  When I added some more code, increasing the size to 241,134 bytes I 
> get a SIGSEGV error when I attempt to initialize a variable.  The routine 
> was scanned with Splint, which showed no errors. When I removed some code, 
> it again ran perfectly.  My feeling is that I have overrun the boundary of 
> the area in which the values of the variables, or possibly the variables 
> themselves, are stored.
> How do I increase these area(s)?

If your variables are stack based, you can increase the stack
size using stubedit for your program (usually 512KB, but
can be changed).  If you are allocating your variables via
new, malloc, or static storage, there is no limit (other than
the amount of memory / paging / dpmi memory available).

If increasing the stack size does not resolve your problem,
then it is some other bug, not sizing related.  Look at the
line number referenced by symify for more details.

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019