Le 27/10/2018 à 11:18, jp charras a écrit : > Le 26/10/2018 à 22:18, Maciej Suminski a écrit : >> What do you think about providing archives with debug symbols for >> Windows builds? It is a platform where we rarely get a stacktrace, >> because the process is not trivial and Windows debug builds take lots of >> space (_pcbnew.kiface is ~1.5 GB on my PC). Normally it would be wasted >> bandwidth, but from time to time we get bug reports which noone else can >> reproduce and then a stacktrace would be of great help. >> >> I have written a patch that adds a CMake flag to split debug information >> to another file. This way we could offer compact binaries to the users >> and ask them to download debug information only in case of serious >> problems. There is already GDB shipped with the nightly installers, so >> then getting a stacktrace becomes feasible or we could use catchsegv [1] >> for an automated approach (see the attached example log; do not worry >> about the null pointer dereference - I added it temporarily to test the >> software). Obviously, Thomas' crash reporter looks even more convenient, >> but it is not mingw-gcc compatible [2]. The patch is also compatible >> with BUILD_SMALL_DEBUG_FILES flag. >> >> I have not pushed the patch yet, as I still wonder whether adding >> another CMake flag is a good idea. Just now I realized that there are >> just a few extra commands to create the needed files, so perhaps they >> could be executed by the build scripts on Jenkins hosts. >> >> Cheers, >> Orson >> >> 1. https://github.com/jrfonseca/drmingw/tree/master/src/catchsegv >> 2. >> https://docs.wxwidgets.org/3.0/group__group__funcmacro__appinitterm.html#ga28a4fb827b93fa6bac18c9666c23ee10 > > Hi Orson, > > I tested your patch without any issue on W7 32 bits and gdb. > > With -DBUILD_SMALL_DEBUG_FILES=ON option, the binaries are about 20 time > smaller than without this option. > > In fact on my 32 bits install, without this option, I cannot load pcbnew > from Kicad or with gdb and load a medium complexity board: I am running > out of memory. > > In countries using a comma as FP separator, there is a problem: > When loading a bitmap, and perhaps some config files, a wxASSERT is > displayed (see attached copy) > I tried to fix this wxWidgets alert, but no luck. Hi Orson,
I just committed a fix to hide the alert dialog message about FP separator in countries using the comma (Windows specific), when reading/writing files. This alert dialog message is overzealous in our case. -- Jean-Pierre CHARRAS _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
