Re: Symbolic tracebacks on Debian

["(see below)" <yaldnif.w@blueyonder.co.uk>]

On 23/05/2010 16:52, in article m2632evcn3.fsf@pushface.org, "Simon Wright"
<simon@pushface.org> wrote:

> Stephen Leake <stephen_leake@stephe-leake.org> writes:
> 
>> Simon Wright <simon@pushface.org> writes:

>>> You need to call
>>> 
>>>    GNAT.Exception_Traces.Trace_On
>>>      (Kind => GNAT.Exception_Traces.Unhandled_Raise);
>> 
>> I never do this.
>> 
>>> from somewhere in your program and run gnatmake with -bargs -E.
>> 
>> I only do this if I want symbolic traces from the running program, which
>> I don't anymore.
> 
> If you want _symbolic_ traces you add
> 
>    GNAT.Exception_Traces.Set_Trace_Decorator
>      (Decorator => GNAT.Traceback.Symbolic.Symbolic_Traceback'Access);
> 
> Actually, there is a difference: this code
> 
>    with GNAT.Exception_Traces;
>    procedure T is
>       Foo, Bar : exception;
>       task T is
>          entry Start;
>       end T;
>       task body T is
>       begin
>          accept Start;
>          raise Bar;
>       end T;
>    begin
>       GNAT.Exception_Traces.Trace_On
>         (Kind => GNAT.Exception_Traces.Unhandled_Raise);
>       T.Start;
>       raise Foo;
>    end T;
> 
> results in
> 
>    $ ./t
> 
>    Unhandled Exception raised
>    Exception name: T.FOO
>    Message: t.adb:16
>    Call stack traceback locations:
>    0x100001577 0x10000141b
>    task t_0000000100800E00 terminated by unhandled exception
>    Exception name: T.BAR
>    Message: t.adb:10
>    Call stack traceback locations:
>    0x100001742 0x10000aa82 0x7fff825fb8b4
> 
> whereas with the Trace_On call commented out, it generates
> 
>    $ ./t
> 
>    Execution terminated by unhandled exception
>    Exception name: T.FOO
>    Message: t.adb:16
>    Call stack traceback locations:
>    0x10000157d 0x10000142b
> 
> so you get to see the unhandled exceptions in tasks too.

Are these features enabled in your OS X port, Simon?
-- 
Bill Findlay
<surname><forename> chez blueyonder.co.uk