I have the same problem. GDB method for debugging:
gdb mingw-get.exe
r upgrade (starts with updating arguments)
GDB will automatically stop at the SIGSEGV (Segmentation Error) signal, which happens to me.
bt (get backtrace) For me this led to a huge return filled with calls:
#5013 0x6f9cdda4 in mingw-get-0!_ZN14pkgXmlDocument19ResolveDependenciesEP10pkgXmlNodeP13pkgActionItem () from c:\MinGW\libexec\mingw-get\mingw-get-0.dll
It looks like a recursion problem that quickly populated the call stack. Please note that the function name is garbled and we do not know the line number. This is the best thing you can do without debugging characters. If you have debugging symbols, GDB output becomes more useful. For most Linux-style packages, you can get debugging symbols in the -dbg package, similar to a split binary package. However, I do not see the debug package for mingw32-mingw-get in the list.
source share