[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:       Martin =?iso-8859-1?q?Gr=E4=DFlin?= <kde () martin-graesslin ! com>
Date:       2010-12-07 19:41:07
Message-ID: 201012072041.14898.kde () martin-graesslin ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tuesday 07 December 2010 20:28:57 Benoit Jacob wrote:
> 2010/12/7 Andreas Pakulat <apaku@gmx.de>:
> > On 07.12.10 11:22:47, Benoit Jacob wrote:
> >> *****
> >> 4. Crash reports handling (KDE: poor, Mozilla: good)
> > 
> >>  * Have a look at Socorro, Mozilla's crash report tool:
> > Your info is outdated I think, try out a KDE 4.5 app crashing. Dr.Konqi
> > improved a _lot_ in the last year or so and its being actively worked
> > on. It does a great job at finding duplicates before you file bugs, it
> > tries to gather additional information from the user and allows to
> > attach info to existing reports instead of creating new ones. And IIRC
> > for 4.6 there's going to be support for installing -dbg packages (a note
> > also already exists since some time if the backtraces are lacking
> > debug-symbols) from the distro when they're missing and re-reading the
> > bt.
> 
> 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?
quite simple: search for product "kwin" with status "RESOLVED" resolution 
"UPSTREAM". That's a 100 % match :-P

Yes that would be very useful especially to be able to direct the crashes 
further. We currently have no way to see which drivers crash a lot and where. 

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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