How do you enable the #ifdef DEBUG sections?
Miklos Vajna
vmiklos at collabora.co.uk
Mon Mar 30 01:24:29 PDT 2015
Hi,
On Sat, Mar 28, 2015 at 02:10:14PM +0200, Tor Lillqvist <tml at iki.fi> wrote:
> If you check the Library_writerfilter.mk in the branch you are looking
> at, you will notice that DEBUG_ELEMENT (and all the other DEBUG_FOO)
> are defined on the compilation command line if gb_DEBUGLEVEL is higher
> than 1. I.e. you need to build writerfilter with 'make writerfilter
> dbglevel=2', I think.
That used to be true in the past, but exactly because usually compiling
with dbgutil is enough for debugging, I changed that with
9401b1be3480037f2dfcb7b6daf069137ccd7c42 (writerfilter: make dmapper
logging a runtime decision, not a buildtime one, 2014-10-16).
Quoting writerfilter/README:
* The incoming traffic of dmapper can be dumped into an XML file in /tmp in
debug builds, start soffice with the
`SW_DEBUG_WRITERFILTER=1` environment variable if you want that.
Regards,
Miklos
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.freedesktop.org/archives/libreoffice/attachments/20150330/0f606153/attachment.sig>
More information about the LibreOffice
mailing list