Yes, that was the same commit I tested as mentioned earlier. Although somehow added a "not" in the original message :)
On Tue, 11 Jun 2019 at 00:52, Wayne Stambaugh <stambau...@gmail.com> wrote: > > Did you test the latest commit 2745a95b6b02c3864d6594503cc21619691cdd94? > > On 6/10/19 6:02 PM, Nick Østergaard wrote: > > It didn't seem to work for the use case I described on windows last week. > > > > On Mon, 10 Jun 2019 at 23:51, Wayne Stambaugh <stambau...@gmail.com> wrote: > >> > >> Hey Tom, > >> > >> On 6/4/2019 12:31 PM, Tomasz Wlostowski wrote: > >>> On 04/06/2019 17:11, Tomasz Wlostowski wrote: > >>> > >>>> Hi Wayne, > >>>> > >>>> It looks like I screwed up the exception handler under KiCad windows > >>>> shell. Will fix soon. > >>> > >>> Fixed in my github branch. > >>> > >>> T. > >>> > >> > >> I just finished testing this on windows (32 and 64 bit) and it appears > >> to work fine when launched from KiCad and stand alone mode. I only > >> tested it using your provided force crash menu entry so I don't know if > >> it will work with a crash other than that. Too bad the gcc windows > >> build crash report doesn't have a stack trace. Maybe MSVC builds would > >> have more debug info. It looks like it's ready to be merged for further > >> testing. > >> > >> Cheers, > >> > >> Wayne _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
