Re: Some comments regardig https://github.com/audacity/audacity/pull/836

James Crook <[email protected]> Tue, 11 May 2021 16:18:31 +0100
Newsgroups gmane.comp.audio.audacity.devel
Message-ID <CAMe=4itirr1U5XBzAp86gCK00o-vZT-svyzdhOhOnrY_ZhRYwg@mail.gmail.com>
Thanks Joost!

That sounds good, and not a contentious use of TCP/IP at all,
especially as explicit opt-in on each and every crash.

Can you say more about the processing at the receiving end??
Lots of time and work on tools there??  My expectation is that
some crashes will have very repeatable stack traces, often due
to a recent change in our code, but some won't, and I wonder
particularly how you dealt with those?

Is it one of those cases where 90% of the benefit comes easily, once
set up, and that alone makes it worthwhile doing?

--James.

On Tue, 11 May 2021 at 15:36, Joost Andrae <[email protected]> wrote:

> Hi,
>
> if you plan to integrate some kind of crash reporting functionality into
> Audacity then this could be integraded without dependencies to external
> libs (on unixoid systems, not on win32 where you might depend on WinDbg
> from MS).
> At OpenOffice.org/StarOffice we had such a functionality. Maybe a short
> look at the impl. might be helpful, just if you're interested into it.
>
> AOO Grok link:
> http://openoffice-vm1-he-de.apache.org/xref/aoo419/main/crashrep/source/
>
> The application implements an event handler to call the strace/pstack
> kernel function in case of a SEGV. Additionaly pmap is called to give
> additional information.
> If you want to have a readable call stack then you need to store the
> unstripped build with debug information to map the stack IDs to those
> from a build with debug information.
>
> Crash information was sent (opt-in at every crash of the application)
> via a soap interface to one server behind a firewall layer. Information
> is stored into a database.
>
> In this case it was possible to map the functional application areas /
> responsible developers to a stack via statistical db lookup on source
> code line level. At the end we defined thresholds on counts of similar
> call stacks to automatically submit a bugzilla bug.
>
> just my 2 EUR Cents....
>
> Kind regards, Joost
>
>
>
>
> _______________________________________________
> audacity-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

_______________________________________________
audacity-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-devel