On Tue, 2010-03-30 at 15:11 +0200, Michael Stahl wrote: > On 30/03/2010 13:31, Terrence Enger wrote: > > ( I think, though, that I am giving up on trying to use a non-product > > build when I actually want to get work done <grin />. ) > > before resorting to such extreme measures as not using non-product builds, > try the debug dialog (Control-Shift-Alt-D). > it lets you change assertion reporting from a dialog box to output on > stderr (the option is called "shell"), or to a window. > you can also increase your level of annoyance by enabling "warnings" as > well :)
Ah, yes that debug dialog. I tried a non-product build with the intention of learning about that dialog. But before getting there, I got caught up in the assertions, and I have yet to get out of the trap. Is there anything that will capture a record of what I did to get into an "interesting" situation? It has happened more than once that I have been trying to reproduced an assertion--but writing down the steps as I go along, so as to produce a good bug report--when I fat-finger something (but I am not sure exactly what) which sends me to a different assertion. Speaking of bug reports ... I have been attaching a backtrace captured while the Debug Output window is open. And I do that with debugging symbols loaded (which *really* loads down my poor little computer). Are these helpful things to do? Does a backtrace compensate for skimpiness in the "steps to reproduce"? Thanks, Terry. > > regards, > michael > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
