Re: [Mingw-users] Pending new mingwrt and w32api releases
- Date: Wed, 1 Mar 2017 18:57:18 -0600
- From: David Gressett <DGressett@xxxxxxxxxxxxxxx>
- Subject: Re: [Mingw-users] Pending new mingwrt and w32api releases
>From: Keith Marshall [mailto:keithmarshall@xxxxxxxxxxxxxxxxxxxxx]
>Sent: Tuesday, February 28, 2017 3:25 PM
>Subject: Re: [Mingw-users] Pending new mingwrt and w32api releases
... snip ...
> It failed, with the crash of a program that is part of the Ada
> build system: xsinfo.exe, located in my build tree at
> xsinfo almost completed successfully; Here are the last few
> lines that it displayed in my msys window:
> "Check for missing functions in body
... snip ...
> All tests completed successfully, no errors detected
>So, it appears that it may have reached the end of it's main()
>function, then failed in the termination code.
>> This application has requested the Runtime to terminate it in
>> an unusual way. Please contact the application's support team
>> for more information."
>That's got to be one of the least useful error messages, ever.
>> The "unusual way" line also appeared in a Windows popup error
>> message box. I will supply more information later as I do more
>> detective work to try to find the cause of the failure.
>Did that popup message box not report a status code? Knowing
>that might have been helpful.
There was no code.
>It's possible that this is some
>sort of latent bug in the xsinfo.exe program itself, just as it
>may be due to some change in mingwrt or w32api. Could you run
>xsinfo.exe under GDB, to determine where it is crashing? Or,
>build mingwrt and w32api from the repository, then run a git
>bisect over the changes since the last 3.x releases?
I know almost nothing about git. My first attempt at
gdb on the offending xsinfo.exe didn't turn up very much.
It is written in Ada. here is what I got on my only attempt
today. I will resume tomorrow:
$ gdb xsinfo
GNU gdb (GDB) 7.6.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "mingw32".
For bug reporting instructions, please see:
Reading symbols from c:\build_gcc-6.3.0_mingw-pkg\workspace\build3\gcc-6.3.0-mingw32\gcc\ada\bldtools\sinfo\xsinfo.exe...done.
Temporary breakpoint 1 at 0x41656f
Starting program: c:\build_gcc-6.3.0_mingw-pkg\workspace\build3\gcc-6.3.0-mingw32\gcc\ada\bldtools\sinfo/xsinfo.exe
[New Thread 18324.0x5ff4]
[New Thread 18324.0x3d6c]
[New Thread 18324.0x769c]
[New Thread 18324.0x5f18]
Temporary breakpoint 1, 0x0041656f in _ada_xsinfo ()
Single stepping until exit from function _ada_xsinfo,
which has no line number information.
Check for field name consistency
Check for function consistency
Check for missing functions
Check for set procedure consistency
Check for missing set procedures
Check pragma Inlines are all for existing subprograms
Check no pragma Inlines were omitted
Check references in functions in body
Check for missing functions in body
Check Set procedures in body
Check for missing set procedures in body
All tests completed successfully, no errors detected
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
[Inferior 1 (process 18324) exited with code 03]
The program is not being run.
>If you can do this, I'll hold off on the release of 5.0 for a
>couple of weeks, until we can glean some useful information
>about this crash.
How tightly bound are the win32api and the mingwrt to each other?
would it make sense to try them one at a time?
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: