[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Thoughts from a former KDE, currently Mozilla developer
From:       Benoit Jacob <jacob.benoit.1 () gmail ! com>
Date:       2010-12-07 20:53:57
Message-ID: AANLkTin1a3_Zckr5vy9OTWADiN3xwbnAw39ANtG7C8v0 () mail ! gmail ! com
[Download RAW message or body]

2010/12/7 Thiago Macieira <thiago@kde.org>:
> On Tuesday, 7 de December de 2010 21:13:53 Benoit Jacob wrote:
>> 2010/12/7 Thiago Macieira <thiago@kde.org>:
>> > On Tuesday, 7 de December de 2010 20:28:57 Benoit Jacob wrote:
>> >> So do crash reports now automatically land in a database that's easy
>> >> to do queries on? (See the web interface provided by Socorro)
>> >>
>> >> If I want to get a list of all KDE crashes that happened in libGL.so*,
>> >> how do I go about that?
>> >>
>> >> Regarding backtraces, as I said in my next email, it's not realistic
>> >> to expect the user to do anything more than click OK, when an app
>> >> crashed on him. So I think that the -dbg packages rather need to be
>> >> used by the server.
>> >
>> > Server-side debug symbols implies uploading the core file to the server,
>> > which may contain a variety of interesting information like user
>> > passwords, credit card numbers, etc. Imagine if kwalletd crashed even.
>>
>> Why would it not be enough to just upload part of the stack?
>>
>> If crash reports had to contain a whole core dump, we sure would be
>> able to send them, given that in Firefox's case that would be hundreds
>> of MBs of data.
>
> How are you going to properly find the stack without debug symbols?
>
> Imagine one frame that didn't keep the frame pointer properly?

If the stack is damaged, then indeed I can't do anything; but that's
not the case in a vast majority of crashes.

Benoit

>
> --
> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
>  Senior Product Manager - Nokia, Qt Development Frameworks
>      PGP/GPG: 0x6EF45358; fingerprint:
>      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
>
>
>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]