On Tuesday, 10 July 2012, Michael Meeks wrote:
On Tue, 2012-07-10 at 15:33 +0200, Noel Grandin wrote:
It seems to be a general thing. Not specific to one test, they all
pause, so I have to enter lots of "r" and "q"
Sure - that is to let you do interactive debugging of the test :-)
if
you don't want that behaviour don't set that variable ;-)
Yeah, that's my point. I set the stack trace flag, (DEBUGCPPUNIT) but not
the interactive flag (
GDBCPPUNITTRACE)
Or have I got that the wrong way around ?
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.