Re: [Kicad-developers] [PATCH] Print stacktrace when SIGSEGV or SIGABRT appears

2018-10-25 Thread Maciej Sumiński
On 10/26/18 2:29 AM, Tomasz Wlostowski wrote: [snip] > I made a variant of the dialog that (hopefully) is easier to understand. > This raises another question: do we have any means of reporting bugs > without forcing the users to register on launchpad, for example a public > Kicad bug email (e.g. b

Re: [Kicad-developers] [PATCH] Print stacktrace when SIGSEGV or SIGABRT appears

2018-10-25 Thread Tomasz Wlostowski
On 25/09/2018 19:53, Thomas Pointhuber wrote: > Hi Wayne, > > thanks for reminder. I implemented a simple compile time switch to allow > maintainers to enable/disable crash reporting. Hi Thomas, I had a look at your branch and I think it's ready to merge with one exception - the default wx crash

Re: [Kicad-developers] 5.1

2018-10-25 Thread Maciej Suminski
Hi Wayne, On 10/25/18 5:17 PM, Wayne Stambaugh wrote: [snip] > I looked at this and it only works for linux. Although it may be highly > unlikely, given that wxpython and wxwidgets can be build against gtk on > windows and msys2 provides gtk2, gtk3, and as of a few days ago gtk4 > packages, there

Re: [Kicad-developers] 5.1

2018-10-25 Thread Wayne Stambaugh
On 10/25/2018 2:37 AM, Maciej Sumiński wrote: > On 10/25/18 2:23 AM, Seth Hillbrand wrote: >> Am 2018-10-24 17:20, schrieb Maciej Suminski: >>> Actually I was pretty sure that my approach is bullet-proof, but perhaps >>> I do not get where the trap is hidden. As far as I understand, Seth >>> experi