So when OOo crashes, what are the strategies that distros employ here if any ?
For RH we don't build the crashreporter (as it's basically unusable info for Sun), but we do configure to enable using it, and replace it in the install set with a simple replacement that tests for the set of common problems that historically caused crashes, e.g. nvidia drivers, a11y enabled, selinux settings and insane local library butchering, and prompts the unfortunate user to log the supplied text to the RH bugzilla, and we map the stack back to source with http://people.redhat.com/caolanm/ooocvs/ooomapstack after throwing out the nvidia driver using reports At some stage in the past the ooobuild OOo would spawn off the gnome gnome bug-buddy, but that's no longer the case is it ? So do other distros have various solutions here, or just simply crash out and/or dump core ? What I'm thinking about aiming at is a shared cross-distro crash repository where we can auto submit the distro OOo crashes, and the distros can plug in their various stack mappers, with quick and dirty gnomebugzilla-alike tooling to merge the duped backtraces together. C. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
