Web lists-archives.com

Re: [Mingw-users] Pending new mingwrt and w32api releases

>From: Eli Zaretskii [mailto:eliz@xxxxxxx] 
>Sent: Sunday, March 05, 2017 1:58 PM
>To: MinGW Users List <mingw-users@xxxxxxxxxxxxxxxxxxxxx>
>Subject: Re: [Mingw-users] Pending new mingwrt and w32api releases

>> From: David Gressett <DGressett@xxxxxxxxxxxxxxx>
>> Date: Sun, 5 Mar 2017 11:31:15 -0600
>> >Eli has already offered some follow-up dialogue on this.
>> I saw that, and proceeded to work on shrinking xsinfo into
>> a minimal test case. When I finished, xsinfo had completely
>> vanished; it is now replaced with CrashDemo.adb, which
>> has only 5 lines of actual code:
>> procedure CrashDemo is
>> Err: exception;
>> begin
>> raise Err;
>> end CrashDemo;
>> It is built with this command line:
>> gnatmake -g CrashDemo
>> This produces the same gdb traceback that I got with xsinfo.

>Ada is not even a read-only language for me, but doesn't the above
>raise an exception that has no handler? If so, the fact that the
>runtime calls 'abort' is expected, I think, as that's what should
>happen when there's an unhandled exception.

It does indeed raise an unhandled exception, but such exceptions
are handled inside the Ada runtime. When crashdemo.exe is built
with the current V3 system libraries, it runs with no crash and exits
with as message saying that it raised CRASHDEMO.ERR. When run
from GDB with a breakpoint set for abort, it runs to completion 
and the break does not happen.

When it is compiled with the V5 prerelease system libraries, it crashes
inside the Ada runtime library before it can produce the CRASHDEMO.ERR
message. When run from GDB with a breakpoint set for abort, the
break does happen.

I have done all of this with both the current MinGW gcc 5.3.0  and with
my experimental gcc 6.3.0, and get the same results with both.

Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
MinGW-users mailing list

This list observes the Etiquette found at 
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

You may change your MinGW Account Options or unsubscribe at:
Also: mailto:mingw-users-request@xxxxxxxxxxxxxxxxxxxxx?subject=unsubscribe