On Wednesday 20 of May 2009, Robert Kaiser wrote:
Stephan Kulow wrote:
Actually the right thing to do is to do the apport way. Meaning to upload the crash informations to a server who has the right debuginfos at hand and can create useful crash logs you can then fill in a bug. No reason to update several GB of data you hopefully only seldomly need.
We're also doing this for official releases (and "nightly" versions published every day) of Firefox, Thunderbird, SeaMonkey here at Mozilla, using the cross-platform open-source "Breakpad" tool and "Socorro" server. Our build machines transfer the symbols to the server, the user only has an optimized build and sends a symbol-less crash stack there, which the server can connect to the symbols again (and even with source lines that can be linked in reports, etc.) It works well and gives good insight into single crash reports as well as statistical overviews of frequent crashes, and it scales well to large amounts of users (or else we couldn't ship every released copy of Firefox with an activated crash reporter). See http://crash-stats.mozilla.com/ for the web interface to the server. I'm pretty sure we'd be happy if other projects start to use that tool as well. :)
Does it work also if I have glibc from 11.1, libX11 from 11.1 updates, kdelibs4 from yesterday's KDE:KDE4:STABLE and kdebase4 one month old from KDE:KDE4:STABLE? -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak@suse.cz , l.lunak@kde.org Lihovarska 1060/12 tel: +420 284 084 672 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org