To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=109142 Issue #|109142 Summary|Let assertions abort Component|porting Version|DEV300m71 Platform|All URL| OS/Version|All Status|NEW Status whiteboard| Keywords| Resolution| Issue type|ENHANCEMENT Priority|P3 Subcomponent|code Assigned to|sb Reported by|sb
------- Additional comments from s...@openoffice.org Thu Feb 11 08:39:11 +0000 2010 ------- Assertions (OSL_ASSERT et al from osl/debug.h, and DBG_ASSERT et al from tools/debug.hxx), if enabled (i.e., doing an --enable-dbgutil build, or building parts of the code with debug=x) should abort (following practices established by C assert.h etc.). Without such a strict measure, the many assertions occurring in a run of OOo (e.g., even executing the smoke test produces lots of them) would probably never go a away, and the assertion tool would remain practically useless (as developers hardly notice assertions newly introduced by their code changes, in the sea of existing ones). --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@porting.openoffice.org For additional commands, e-mail: issues-h...@porting.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
