Getting good debugging stack traces from wine apport crash reports

[Martin Pitt]

Hello fans of wine,

I already sent this to Scott Ritchie a while ago, but didn't get a
reply, so let's try here.

When we talked about improving apport to deliver better stack traces
to us in Sevilla [1], someone also mentioned that wine upstream currently
refuses our gdb stack traces for wine crashes. They want to have some
special magic applied to it instead.

Who would be an appropriate person and/or ML to discuss this with? I
am happy to work with someone to get a good solution for this, but
since I have zero knowledge about wine I cannot do this alone.

As the spec [1] says in point 6, we can either silence apport for wine
completely (easy solution, I can do it myself), or find someone who
has a clue about debugging wine and winedb who wants to write a proper
apport hook for wine crashes.

Did someone get curious now? :-)

Thank you!

Martin

[1] https://wiki.ubuntu.com/ApportBetterRetracing

-- 
Martin Pitt        http://www.piware.de
Ubuntu Developer   http://www.ubuntu.com
Debian Developer   http://www.debian.org