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=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,534dd301375921ac
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.193.129 with SMTP id ho1mr3339476pbc.8.1339700170284;
        Thu, 14 Jun 2012 11:56:10 -0700 (PDT)
Path: 
 l9ni50841pbj.0!nntp.google.com!news1.google.com!news2.google.com!news.glorb.com!news.netfront.net!not-for-mail
From: Jeffrey Carter <spam.jrcarter.not@spam.not.acm.org>
Newsgroups: comp.lang.ada
Subject: Re: Is Text_IO.Put_Line() thread-safe?
Date: Thu, 14 Jun 2012 11:56:05 -0700
Organization: Also freenews.netfront.net; news.tornevall.net
Message-ID: <jrdc48$14h2$1@adenine.netfront.net>
References: <93201f1a-d668-485e-83b4-492bc283f36e@googlegroups.com>
NNTP-Posting-Host: 184.20.201.198
Mime-Version: 1.0
X-Trace: adenine.netfront.net 1339700169 37410 184.20.201.198 (14 Jun 2012
 18:56:09 GMT)
X-Complaints-To: news@netfront.net
NNTP-Posting-Date: Thu, 14 Jun 2012 18:56:09 +0000 (UTC)
User-Agent: Mozilla/5.0 (X11; Linux i686;
 rv:12.0) Gecko/20120430 Thunderbird/12.0.1
In-Reply-To: <93201f1a-d668-485e-83b4-492bc283f36e@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date: 2012-06-14T11:56:05-07:00
List-Id: <comp.lang.ada>

On 06/14/2012 05:53 AM, awdorrin wrote:
>
> One module is called 'Common' and is a central 'shared memory' location. The
> other modules will call functions in Common to request chunks of memory in
> which to store data structures.
>
> As the modules initialize themselves, they call another routine in Common to
> wait until all tasks are ready (basically there is an array defined in common
> which has an element for each module, the module's corresponding element is
> set when the module is ready to proceed.)

This design sounds suspect to me. Everything in Common needs to be protected if 
it's being accessed by multiple tasks.

> I was having issues with this 'rendezvous' mechanism, because one of the
> modules was dying and all the other tasks were waiting on it, without giving
> any indication, so I added a Text_IO.Put_Line() to print some debug
> information.
>
> Text_IO.Put_Line( Proc_Enum'Image(thisPID)&" waiting for"&
> Proc_Enum'Image(waitPID));

Is this in Common, or in the tasks that use Common?

-- 
Jeff Carter
"English bed-wetting types."
Monty Python & the Holy Grail
15

--- Posted via news://freenews.netfront.net/ - Complaints to news@netfront.net ---