2017-01-16 11:55 GMT+01:00 Miklos Vajna <vmiklos@collabora.co.uk
<mailto:vmiklos@collabora.co.uk>>:
On Fri, Jan 06, 2017 at 10:56:04AM +0100, Tomáš Chvátal
<tomas.chvatal@gmail.com <mailto:tomas.chvatal@gmail.com>> wrote:
> Ah now i get it. Well it happens always on the same test:
>
> [ 649s] trying to instantiate implementation
> "com.sun.star.wizards.agenda.CallWizard"
> [ 649s] unknown:0:(anonymous namespace)::Test::test
> [ 649s] uncaught exception of type std::bad_alloc
> [ 649s] - std::bad_alloc
Here is how I would continue debugging this. Add this after the
SAL_DEBUG() that prints the service name:
if (i.first == "com.sun.star.wizards.agenda.CallWizard")
SAL_DEBUG("foo");
Then in gdb you can put a breakpoint on the SAL_DEBUG("foo"); line,
before the test attempts to instantiate
com.sun.star.wizards.agenda.CallWizard. When you hit the breakpoint, do
"catch throw" and "continue". Hopefully that'll show us where
std::bad_alloc is thrown.
Hi, got to it and attaching the trace of the point. Seems like if I just
break there and then catch the bad_alloc it stops on the right place
finaly :)
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.