[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:14:38
Message-ID: AANLkTimVBzTpcy8W5pBEmmS-v+e420QgLxnzi2orN7tZ () mail ! gmail ! com
[Download RAW message or body]

2010/12/7 Benoit Jacob <jacob.benoit.1@gmail.com>:
> 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,

Sorry, I meant: we sure would NOT be able to send them,

> given that in Firefox's case that would be hundreds
> of MBs of data.
>
> Benoit
>
>>
>> Not to mention that some core files are quite big to upload and store.
>>
>> --
>> 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]