[Libreoffice] [Fwd: Re: [PATCH] cppcheck warning in sw/source/ui/uiview/viewprt.cxx]

[David Tardon]

On Tue, Oct 05, 2010 at 08:38:43AM -0600, Tor Lillqvist wrote:
> > hmmm build debug=t always has worked for me on windows to get the VS
> > debugger to work
> 
> Yep, for me too. never used any dbgutil thing, as far as I can recall.
> 
> (I have noticed that if you build some of the lower-level modules with debug=true, you get lots of pointless assertions for situations that the code handles just fine anyway. But I guess this is no news to you.)

debug=true sets OSL_DEBUG_LEVEL and DBG_LEVEL to 2, which means you
don't get just assertions, but also traces (OSL_TRACE). If you just
built with --enable-dbgutil, you wouldn't see more than a handful on a
run (and usually not even that). But, in a pitch, setting dbglevel=1
should help as well.

As to the other part of your sentence: that the code handles some
situation (in the context where assertions are involved, it usually
'handles' it by ignoring it) doesn't necessarily mean you don't want to
know it happened.

D.