On Wednesday 20 of May 2009, Marcus Meissner wrote:

On Tue, May 19, 2009 at 07:44:04PM -0400, Greg Freemyer wrote:

...

On Tue, May 19, 2009 at 7:16 PM, Sascha 'saigkill' Manns Make sense, except the debugsource files are huge. I have a T-1 here to download with and iirc it takes about 30 minutes to get them. Not my favorite experience, but without them the crash logs are useless.

Maybe the true factory set should have that dependency, but the version for 11.1 should not?

You actually would want the -debuginfo for better backtrace, not the -debugsource.

However the recommended way is:

If you see a crash-> install debuginfo packages -> recreate the crash

That is actually not necessary with KDE4.3. There is a time between the crash and the time the backtrace is analyzed, at which point it is sufficient to install the needed debuginfo packages, and there is even a button for recreating the backtrace if it turns out more debuginfo packages are needed. I expected there would be also support for automatically getting the needed debuginfo packages installed using zypper, but that hasn't made it in KDE4.3.

Sometimes it might not be recreatable, but then you have debuginfos installed and it will be a better backtrace the next time around. (You could actually install the debuginfos before you get the backtrace window in drkonqi, but this is a bit more complicated.)

-- 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

Am Mittwoch 20 Mai 2009 09:39:30 wrote Marcus Meissner:

On Tue, May 19, 2009 at 07:44:04PM -0400, Greg Freemyer wrote:

...

On Tue, May 19, 2009 at 7:16 PM, Sascha 'saigkill' Manns

wrote:

...

Hello Mates,

just a though: With KDE4.3pre we have an better Crashmanager. After an Crash he creates an Crashlog and then you can submit an Bugreport to KDE. My Idea now is, that we can make the depency to the debugsource Package per default. Some Guys, who are using openSUSE maybe don't know that without debugsurce the Crashlog are bad. -- Sincereley yours

Sascha Manns

Make sense, except the debugsource files are huge. I have a T-1 here to download with and iirc it takes about 30 minutes to get them. Not my favorite experience, but without them the crash logs are useless.

:(

Maybe the true factory set should have that dependency, but the version for 11.1 should not?

You actually would want the -debuginfo for better backtrace, not the -debugsource.

However the recommended way is:

If you see a crash-> install debuginfo packages -> recreate the crash Aha. Ok. That was just a though...

-- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com

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