From mboxrd@z Thu Jan  1 00:00:00 1970
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Kevin Chadwick <kc-usenet@chadwicks.me.uk>
Newsgroups: comp.lang.ada
Subject: Unpropagated exception handling on zfp
Date: Fri, 3 Nov 2023 18:56:59 -0000 (UTC)
Organization: A noiseless patient Spider
Message-ID: <ui3fpr$2t7kq$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 3 Nov 2023 18:56:59 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="bef5d5f89874f91266e8b81092c46e45";
	logging-data="3055258"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18LYQpV4XRqnLpeqH1d4uWtYQs+52/6AeM="
User-Agent: PhoNews/3.13.1 (Android/13)
Cancel-Lock: sha1:AkPcSncqDBppxwG1kHQBkekCk3o=
Xref: news.eternal-september.org comp.lang.ada:65831
List-Id: <comp.lang.ada>

On zfp with no exception propagation. You can use a local exception handler
 to return thereby avoiding the last chance handler for this one procedure
 or even exception type.

Obviously it would be better to take the time and prove an absence of
 runtime errors.

However, when you do not have that time. I believe it is not risky if you
 are sure the stack will be cleaned up upon return. Indeed the handler can
 return or set known safe values. I assume that out of bounds writes are
 caught by constraint checks before they occur? Sometimes you do not want to
 reset the micro but just drop some functionality by return but would still
 like to get the exception message to log.

The only issue is that I cannot see how to get to the exception messages
 System.Address except via the last chance handler. zfp does not permit
 exception propagation and so the Exception_Occurence cannot be used.

Is it possible with gnat 13, even if I need to enable the secondary stack,
 just for this capability?

-- 
Regards, Kc