Bernhard Übelacker

debugging using gdb on windows is plain impossible (it is so slow its not funny anymore, it takes literally hours for it to even start up) Having all libraries with debug information may give gdb a big slowdown. Therefore it could help to have only that executable/shared library/dll with debug information in place that is really needed for this debug task. Unfortunately there do not exists debug symbol packages for msys2 as far as I know. I'd rather not mess with the bindist scripts, as that stuff...

I made a small test with a simple test binary - and unfortunately the --strip-debug did not work as I expected - the backtrace did no longer show function names. In that regard I was after something similar to clang's -gline-tables-only, but it looks like this does not exist for gcc. Thanks for looking into it.

I get also a backtrace with winedbg with wine-11.4: Backtrace: =>0 0x006ffff8a0d011 ID2D1Image_AddRef(This=<internal error>) [/usr/src/packages/BUILD/include/d2d1.h:3254] in d2d1 (0x007fffffa81318) 1 0x006ffff8a0d011 d2d_effect_SetInput+0x21(iface=<register RSI not accessible in this frame>, index=<register RBX not accessible in this frame>, input=<register RDI not accessible in this frame>, invalidate=<internal error>) [/usr/src/packages/BUILD/dlls/d2d1/effect.c:2805] in d2d1 (0x007fffffa81318)...

Wanted to try the network play, but the current Debian package misses the menu entry. The SDL build starts up fine :-) Only the GTK windows build crashes instantly, but that is an issue that needs to be handled at Wine side. Thread 4 "pool-1" received signal SIGSEGV, Segmentation fault. [Switching to LWP 491] 0x00006ffff843d011 in ?? () (gdb) add-symbol-file /opt/wine-devel/lib/wine/x86_64-windows/d2d1.dll 0x6ffff8421000 Reading symbols from /opt/wine-devel/lib/wine/x86_64-windows/d2d1.dll... (gdb)...

Leave minimal debug symbols in windows builds.

Increase version in Debian packaging.

Release version 1.4.0.

Update README.