From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,444c1179ce493ca2
X-Google-Attributes: gid103376,public
From: Brian Crouch <bcrouch@msmail2.hac.com>
Subject: Re: Vads X/Motif & C
Date: 1996/09/11
Message-ID: <3236C48D.75F9@msmail2.hac.com>#1/1
X-Deja-AN: 180020793
references: <514579$sts@news.sei.cmu.edu>
content-type: text/plain; charset=us-ascii
organization: Hughes Aircraft Co
mime-version: 1.0
newsgroups: comp.lang.ada
x-mailer: Mozilla 2.01 (Macintosh; I; 68K)
Date: 1996-09-11T00:00:00+00:00
List-Id: <comp.lang.ada>


Mark Bell wrote, in part:
> 
> However, I'm still getting segmentation faults during various
> X/Motif calls, and I'm not 100 percent sure that the above
> fix has totally addressed the problem of the interaction of the
> Vads Ada runtime and Solaris OS in regards to memory allocation.
> Does anyone have any "lessons learned" from doing similar work ??
>

Does your program use tasking?  If so, you should try increasing the 
task storage space by using the 'STORAGE_SIZE attribute on the task 
type.  The default task storage space in my Sun Ada environment 
(which should be the same as your Vads) is only 10K which can 
quickly be eaten up in a Motif program.