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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,6bd623312637f478
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.180.94.98 with SMTP id db2mr1339844wib.2.1351391042012;
        Sat, 27 Oct 2012 19:24:02 -0700 (PDT)
Path: 
 q13ni70610wii.0!nntp.google.com!feeder3.cambriumusenet.nl!82.197.223.108.MISMATCH!feeder2.cambriumusenet.nl!feeder1.cambriumusenet.nl!feed.tweaknews.nl!94.232.116.13.MISMATCH!feed.xsnews.nl!border-3.ams.xsnews.nl!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!nntp.giganews.com!news.panservice.it!feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Okasu <oka.sux@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: ZLIB_ERROR with AWS
Date: Sat, 20 Oct 2012 08:32:02 +0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <slrnk84oah.pm3.oka.sux@localhost.localdomain>
References: <slrnk83sci.9vf.oka.sux@localhost.localdomain>
 <slrnk84kap.ln5.oka.sux@localhost.localdomain>
 <1rlmakeghhe91$.j7n87jxwku6w.dlg@40tude.net>
Mime-Version: 1.0
Injection-Date: Sat, 20 Oct 2012 08:32:02 +0000 (UTC)
Injection-Info: mx04.eternal-september.org;
 posting-host="bc9127a96e16ddc323f05fe298adcf6a";
	logging-data="29257"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19zF00MGA29XIhlO9f1uYY0"
User-Agent: slrn/0.9.9p1 (Linux)
Cancel-Lock: sha1:DUEVQUUVnALEzRFmUb8MsD2ofLQ=
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: 2012-10-20T08:32:02+00:00
List-Id: <comp.lang.ada>

On 2012-10-20, Dmitry A. Kazakov <mailbox@dmitry-kazakov.de> wrote:
> No, it looks like a typical problem of the clean up involving controlled
> types. That is when an exception is propagated amidst of some process
> involving controlled objects in possibly not a coherent state. So that when
> the propagation starts kicking them out of existence a call Finalize may
> fail. That turns the original exception into Program_Error. This stuff is
> barely testable, because one cannot foresee and emulate all possible
> exceptions at all possible places. I bet that almost any Ada program has
> issues of this kind. So, it is a bug, but not the original problem.

What bug are you talking about? Issue with zlib or finalize/adjust with HTTPS
issue? Can you suggest workaround (without involving another
language)?