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
Caolan McNamara wrote:
Hi Caolan,
[... snip ...]
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
Caolan McNamara wrote:
So when OOo crashes, what are the strategies that distros employ here if
any ?
Sun has a SOAP receiving service for crash reports, a database to store
crashreports, a daemon service which tries to find similiar stacktrace
based on the information send in the XML file
On Fri, 2007-05-18 at 15:43 +0200, Bernd Eilers wrote:
Caolan McNamara wrote:
So when OOo crashes, what are the strategies that distros employ here if
any ?
Sun has a SOAP receiving service for crash reports,
I'm aware of the tooling there, but this is somewhat orthogonal as the
Sun
ReHi,
Caolan McNamara wrote:
On Fri, 2007-05-18 at 15:43 +0200, Bernd Eilers wrote:
Caolan McNamara wrote:
[... snip ...]
Certainly there may be issues of scalability and it may be impractical. I was thinking
of whipping something Red Hat specific together and giving it a whirl
Caolan McNamara wrote:
On Fri, 2007-05-18 at 16:23 +0200, Bernd Eilers wrote:
Caolan McNamara wrote:
Hi Caolan,
ReHi,
As far as I have heard there are distributions which currently do not
release from MasterWorkspaces or ChildWorkspaces but do in fact use some
kind of more or less
