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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.236.53.170 with SMTP id g30mr18331836yhc.17.1433019441711;
 Sat, 30 May 2015 13:57:21 -0700 (PDT)
X-Received: by 10.140.38.102 with SMTP id s93mr203583qgs.37.1433019441666;
 Sat, 30 May 2015 13:57:21 -0700 (PDT)
Path: 
 buffer2.nntp.dca1.giganews.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!z60no4723813qgd.1!news-out.google.com!k20ni45034qgd.0!nntp.google.com!z60no4724693qgd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sat, 30 May 2015 13:57:21 -0700 (PDT)
In-Reply-To: <lyh9qt98nb.fsf@pushface.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=105.237.62.132;
 posting-account=orbgeAkAAADzWCTlruxuX_Ts4lIq8C5J
NNTP-Posting-Host: 105.237.62.132
References: <41913ae0-7513-4be5-bb94-b834836f8525@googlegroups.com>
 <87617at8ub.fsf@adaheads.sparre-andersen.dk>
 <dba41328-610e-4189-8656-77e5b808f138@googlegroups.com>
 <lyh9qt98nb.fsf@pushface.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <0a552a83-8666-4d80-b0e4-b8cdd32f42b0@googlegroups.com>
Subject: Re: Arm - ravenscar - exceptions - last chance handler
From: jan.de.kruyf@gmail.com
Injection-Date: Sat, 30 May 2015 20:57:21 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref: number.nntp.giganews.com comp.lang.ada:193417
Date: 2015-05-30T13:57:21-07:00
List-Id: <comp.lang.ada>

On Saturday, May 30, 2015 at 9:18:18 PM UTC+2, Simon Wright wrote:

> > And from experience: my Arm board just kick the bucket on an
> > exception, afterward I learned to put a break point in the last chance
> > handler. Then I could see the string in memory.
> 
> Hence the loop-forever (which is also the way that FreeRTOS handles
> (some) unrecoverable errors); things stop working, C-c in gdb, poke
> around.

I think it kicks the bucket because a null reference in the raise exception call
in other words it does not come to last_chance_handler in the regular way you expect. But in anycase the end effect is the same.