Hi Joost, On Tue, May 29, 2012 at 03:01:27PM +0200, Joost Andrae wrote: > Hi, > > the soap service shouldn't be that problem as it is documented here: > http://wiki.services.openoffice.org/wiki/CrashReporting#How_does_the_Tool_work_internally.3F > > The soap service uses the following header: > > public static String submitReport(SOAPContext soapContext,String > body, Hashtable attachments ) > > The format of a crash report has been specified here: > http://porting.openoffice.org/crashrep/errormail_xml.sxw
thanks for the information, very useful. > >We should think about enabling the feature. May be we cannot bring the > >SOAP service again, but we can: > > > >- use the default system mail client to send the crash report to > > ooo-private > >- simply let the user save the crash report and send it manually > >- automatically submit a bug if the user has a bugzilla account > > You know that you need a compatible pdb file of that build to get > useful information of the stack data ? Most probably you need a > memory mapping table as well... I've no idea about Windows, never tried the crashrep there. In Linux at least it is not that hard to get something useful of the it. > Sending this via email might spam > the email account... I was thinking of something similar to what ABRT does on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=708361 That bug was submitted by the ABRT tool, it only prompts for the bugzilla user and password, plus the description of what you where doing when the error occurred. IMHO, the automatic bug submittion is useful besides the usefulness of the stack trace. Regards -- Ariel Constenla-Haile La Plata, Argentina
pgpDnUnHYIjqo.pgp
Description: PGP signature
