On 15/12/11 11:49, Michael Meeks wrote: > On the other hand, windows being windows & hence #$%#$5ing useless has > no means for us to get a stack trace that might help with debugging. > > At least - I heard in the past that this was possible, and/or easy and > you 'only' have to <insert ten un-documented steps> ;-) > > Tor / Pedro - is there documentation for Windows for how to get a stack > trace for our Betas ? and/or can we get one for this ? FWIW, the wine > version appears not to even start impress ;-)
OOo used to have a crash reporter that produced stack traces (in hex, of course, so you need pdb files or something to make use of it, we had some internal tool to do that iirc...) actually i think the Windows stack traces were useless since OOo 3.3 because of the (non-)rebasing at install time to improve startup performance, or at least the internal tool refused to run because the checksums of the libraries were wrong... _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
