Hey,
so I had the joy of debugging one of the perfcheck tests and noticed that
running them normally under gdb does not work (valgrind and gdb don't play
nice with each other by default). However there is a gdbserver built into
valgrind so we now have VALGRIND_GDB which if set to TRUE will start the
valgrind gdb server and wait for a connection. You can then connect to the
test from a gdb instance started with
gdb workdir/LinkTarget/Executable/cppunittester
and inside of gdb
target remote | vgdb
After that you are connected to the valgrind gdbserver and can start
debugging the test.
Regards,
Markus
P.S. In theory you can query the gdbserver for leaked memory when you run
memcheck but the last time I tried that it reported a lot of potentially
leaked memory.
Context
- debugging tests running under valgrind (e.g. perfcheck) · Markus Mohrhard
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.