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.
I'd like to avoid having my end-users have to install the entire msys2 package. What I do is build a working copy of things in the Program Files (x86)\ directory, then turn that into an installer and distribute it to my end users. Makes it easier to install for them and only gives them the subset of msys2 stuff that my app requires. Anyway, if I add C:\msys64\mingw32\lib;C:\msys64\mingw32\bin; to my path, like .libs/app_ltshwrapper script, it does not fix the crash... I could use advice on: 1. How to figure out in advance what mingw32/bin and /usr/bin DLLs to package with my application (I presently copy them into the Program Files (x86)\app\bin directory so that my app has access to them without having to install the entire msys2 system). 2. How to figure out after a crash what DLL is missing that causes my app to be unhappy. I have tried: objdump -t exe-name, it reports no symbols in the dynamic symbol table. This is strange since the executable is 76MB and I'm sure it has symbolic information compiled into it. nm -D exe-name, it reports no symbols ldd exe-name reports ntdll.dll and a few wow64 dlls, and a ??? dll, but that's it procmon reports a ton of information and I cannot figure out which is relevant 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. strace from the command line doesn't show enough detail for me to know what is causing the problem--it just shows an access violation 0xc0000005 at 000000000028FE1F and I'm not sure where this comes from gdb starts the program, but when it catches the SIGSEGV, I type 'bt' to see where in the stack I am, and gdb dies like it cannot access that address either. Thanks for any help you can provide. ------------------------------------------------------------------------------ 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