The Cooperative Bug Isolation Project is a joint effort by UC Berkeley and Stanford to bring debugging into the Internet age. Instrumented applications send feedback to our analysis center, where we use statistical debugging techniques to learn what goes wrong when the software crashes.
The project is please to announce that the following instrumented applications are available for Fedora Core 2:
- Evolution 1.4.6 - Gaim 1.0.0 - The GIMP 2.0.5 - Nautilus 2.6.0 - Rhythmbox 0.8.7 (includes iPod & Dashboard support!) - SPIM 7.0
What we need most of all are more runs from real users like you! Even if you've never written a line of code in your life, you can help make things better for everyone simply by using our special bug-hunting packages. Read more, download some packages, and join in!
Fedora Core 1 users can help too: see the downloads page for comparable versions of all of the above applications for FC1.
project info: http://www.cs.berkeley.edu/~liblit/sampler/ downloads: http://www.cs.berkeley.edu/~liblit/sampler/downloads/
Hi
Is it possible to get debugging packages for software in FC3t2? Most important for desktop (and with problems now) are gnome-panel and evolution.
Having some packages for test releases would be great, as it would help debugging. Me for example installed fc3t2 and not going back to FC2.
Is there anything else to do when seeing an application packaged by you crashing? Or it's all automatic?
Thank you,
Marius Andreiana asked:
Is it possible to get debugging packages for software in FC3t2?
Unfortunately, we're not planning to post FC3t2 packages right now. That is due in part to limited manpower and in part to our need for a large user base.
To clarify that second requirement, we don't look at individual failures. Rather, we hunt for bugs by mining statistical *trends* out of large numbers of runs. I'm not convinced that there are enough FC3t2 users to produce the kind of numbers we would need. I do understand that this is where the most unstable code lives, but it's not where the most users live, and our techniques really depend on having lots of users.
Now, if the Fedora engineering team wanted make this part of the standard Fedora build process, so that *every* test release user would be getting our instrumented code, that would be a whole other story....
Is there anything else to do when seeing an application packaged by you crashing? Or it's all automatic?
You make a one-time choice to opt in or out of the system (http://www.cs.berkeley.edu/~liblit/sampler/learn-more/privacy/first-time.png). After that, it's all automatic.
Thanks for your interest and questions, Marius.
-
Ben Liblit -
Marius Andreiana