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

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