kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #41588
Re: [PATCH] Crash Reporter
Hmm, ok, I guess you mean the -may27 one.. it seem to have never commits.
https://github.com/twlostow/kicad-dev/tree/tom-crash-reporter-may27
On Tue, 16 Jul 2019 at 11:08, Tomasz Wlostowski
<tomasz.wlostowski@xxxxxxx> wrote:
>
> On 15/07/2019 14:43, Nick Østergaard wrote:
> > Remind me, is this feature still in a seperate branch to master, or
> > how is it enabled?
>
> IIRC it's still tom-crash-reporter on my github and it's enabled in
> CMake config (KICAD_CRASH_REPORTER=yes).
>
> T.
>
> >
> > On Thu, 11 Jul 2019 at 21:08, Nick Østergaard <oe.nick@xxxxxxxxx> wrote:
> >>
> >> @Tomasz Wlostowski I just found that it looks like someone has
> >> uploaded a wxwidgets 3.1 pkgbuild for the mingw-packages for msys2, I
> >> could try to build and and rebuild your branch for windows.
> >>
> >> https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-wxWidgets3.1/PKGBUILD
> >>
> >> On Tue, 9 Jul 2019 at 14:09, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
> >>>
> >>> Tom,
> >>>
> >>> On 7/9/19 2:41 AM, Tomasz Wlostowski wrote:
> >>>> On 06/07/2019 21:10, Ian McInerney wrote:
> >>>>> Tom,
> >>>>>
> >>>>> Not to pile on the questions, but does the linux stack trace support
> >>>>> exist in the entire 3.0.x line, or how far back does it go? Currently,
> >>>>> the minimum version searched by cmake is 3.0.0, and some major linux
> >>>>> distros only have 3.0.2 (Debian Stable, EPEL6/7, and Ubuntu 16.04 to
> >>>>> name a few).
> >>>>
> >>>> Hi,
> >>>>
> >>>> Under liunx stack trace works fine in 3.0.2. Under Windows it's not
> >>>> implemented at all (unless using a crazy hack self-exception-raising
> >>>> hack that works only under MSVC).
> >>>>
> >>>> I can work this around by having our own Windows stack walker - after
> >>>> all the whole purpose of the crash reporter was easy debug reports for
> >>>> Windows users. Under Linux everyone knows how to use a debugger,
> >>>> otherwise it's impossible to work ;-)
> >>> I'm assuming that you mean that you are going to pull the
> >>> wxDebugReporter code from the 3.1 branch of wxWidgets which can be
> >>> removed once wxWidgets 3.2 becomes the default. If it's any more than
> >>> that, I would rather wait until 3.2 is available.
> >>>
> >>>>
> >>>> Tom
> >>>>
> >>>
> >>> _______________________________________________
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References
-
[PATCH] Crash Reporter
From: Tomasz Wlostowski, 2019-04-14
-
Re: [PATCH] Crash Reporter
From: Nick Østergaard, 2019-06-10
-
Re: [PATCH] Crash Reporter
From: Wayne Stambaugh, 2019-06-10
-
Re: [PATCH] Crash Reporter
From: Nick Østergaard, 2019-06-11
-
Re: [PATCH] Crash Reporter
From: Tomasz Wlostowski, 2019-06-12
-
Re: [PATCH] Crash Reporter
From: Nick Østergaard, 2019-06-12
-
Re: [PATCH] Crash Reporter
From: Nick Østergaard, 2019-07-01
-
Re: [PATCH] Crash Reporter
From: Tomasz Wlostowski, 2019-07-04
-
Re: [PATCH] Crash Reporter
From: Wayne Stambaugh, 2019-07-05
-
Re: [PATCH] Crash Reporter
From: Ian McInerney, 2019-07-05
-
Re: [PATCH] Crash Reporter
From: Carsten Schoenert, 2019-07-06
-
Re: [PATCH] Crash Reporter
From: Tomasz Wlostowski, 2019-07-06
-
Re: [PATCH] Crash Reporter
From: Ian McInerney, 2019-07-06
-
Re: [PATCH] Crash Reporter
From: Tomasz Wlostowski, 2019-07-09
-
Re: [PATCH] Crash Reporter
From: Wayne Stambaugh, 2019-07-09
-
Re: [PATCH] Crash Reporter
From: Nick Østergaard, 2019-07-11
-
Re: [PATCH] Crash Reporter
From: Nick Østergaard, 2019-07-15
-
Re: [PATCH] Crash Reporter
From: Tomasz Wlostowski, 2019-07-16