Hi Canghua, On Wednesday, 2007-05-30 17:15:10 +0800, Canghua Qu wrote:
> Hi,All, > > As we add some features and fixed some bugsof OOo, sometimes our new version > is unstable for unknown reason. I want to know if OOo's developers or testers > use any useful testing ?0?2tools to test the stability such as memory leak. > And > How to deal with such prolbems? You may have noticed the ongoing discussion in another tyhread on this mailing list with subject "Can we do more regression testing?". > BTW, any suggestion is welcomed! Thanks in advance! You'll find information about OOo automated test tools under http://qa.openoffice.org/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomation.html For general code tests that detect access of memory and such please see http://wiki.services.openoffice.org/wiki/Valgrind If you suspect some particular class to have leaking in the sense of instantiations not destroyed, you may temporarily derive it from class ::rtl::DebugBase, see sal/inc/osl/diagnose.hxx Some memory leaks you only find with an adapted memory manager and good knowledge of the application to be able to ignore false positives (not every apparent leak is an unintended real leak). You may compile sal/rtl/source/alloc.c with debug=t You should also build a non-product version (configure --enable-dbgutil) for development and use OSL_ASSURE and similar macros to gather information about your objects. These tests are executed in product versions. Product and non-product builds can be done from the same source tree, the output goes into different directories (without .pro extension for the non-pro version). However, before configuring the non-pro, backup your existing *Env.Set* files to not have them overwritten. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to this [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
