Re: Exception traceback when using TDM-GCC 5.1.0-3

[Simon Wright <simon@pushface.org>]

ahlan@marriott.org writes:

> Our problem is that we don't get a traceback at all.
> In AdaCore's GNAT the traceback is displayed by default in hex.
> To convert that into a symbolic traceback we use Gnat.Traceback.Symbolic.
> However this is not the problem.
> The problem is that we don't get a traceback at all - ie the -E switch
> doesn't seem to have the desired effect.

Using 32-bit TDM GCC 5.1.0 (tdm-1) on Windows 7 with this:

   procedure CE is
      procedure Raiser (N : Positive) is
      begin
         Raiser (N - 1);
      end Raiser;
   begin
      Raiser (5);
   end CE;

I get this:

   >ce

   Execution terminated by unhandled exception
   Exception name: CONSTRAINT_ERROR
   Message: ce.adb:4 range check failed
   Call stack traceback locations:
   0x401533 0x401533 0x401533 0x40154b 0x4014e6 0x4010fb 0x77a73646 0x77a73619

and I can use the addr2line.exe that came with GNAT GPL 2014 (I just
haven't got round to installing the 2016 release) to get this

   >addr2line.exe -e ce.exe 0x401533 0x401533 0x401533 0x40154b 0x4014e6 0x4010fb 0x77a73646 0x77a73619
   C:\Users\Simon Wright/ce.adb:4
   C:\Users\Simon Wright/ce.adb:4
   C:\Users\Simon Wright/ce.adb:4
   C:\Users\Simon Wright/ce.adb:7
   C:/Users/Simon Wright/b~ce.adb:140
   crt1.c:?
   ??:0
   ??:0