"Matthew A. Postiff" <posti...@comcast.net> writes: > I'm stuck trying to figure out a crash that I think is related to a > missing DLL. One clue is that my application worked fine, but then some > upgrades in msys/mingw32 did something underneath my app that is > activating the crash.
If the application, freshly compiled, no longer works with msys/mingw32 in the PATH, the "missing DLL" hypothesis looks weak to me. [snip] > Dependency Walker shows a few missing dlls, but they are > api-ms-win-core-*, dcomp.dll, and ieshims.dll, which I have determined > are not a problem for my application. I am quite sure of this because an > earlier edition of the program that still works (with an older edition > of msys2 from June 2016) and it shows the same depends errors. Use Dependency Walker in "tracing" mode, for detecting missing DLLs which are loaded by the program itself (rather by the OS linker): open you .exe with DW and use Profile to set a command line and run the executable. If any .DLL is missing, DW will report it. Also, https://github.com/achadwick/styrene may be of interest to you. But I think that your problem is not related to missing dlls. [sni] ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel _______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
