Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


On Thu, 2010-10-28 at 11:17 +0200, Thorsten Behrens wrote:
Caolan McNamara wrote:
register component 'configmgr.uno.so' in registry 
'../../unxlngx6.pro/misc/qa_unit/services.rdb' failed!
error (CannotRegisterImplementationException): loading component library failed: 
configmgr.uno.so

Can you (git pull bootstrap) and try export DEBUGREGCOMP=1 and run dmake
in that dir to get a log of the try and catches 

Thing was, this did not usually happen when simply building there -
only during full builds, so I suspect some race...
...anyhow, after the pull no longer happens, instead there's a crash
in the number formatter, see second gdb log (the first has the
successful regcomp run, for archival).

Smells a bit like incomplete uno type info or something, I recall
having similar funny crashes when doing minimal uno runtime fakeage
in vcl.

Hmm, sort of looks like the underlying cppu stuff, or something it uses,
got pulled out from under it during the test. I don't think it could
have gotten that far for the uno::sequence dtor (which looks up the type
of its argument) to blow up without the type system working earlier.

So maybe some other build process is modifying the shared .rdb files,
poking at the testtools bridge test which noone ever complains about and
which is run every time I see it simply copies the .rdb locally, so that
might be worth a shot as an experiment, so pushed that for a test now.

C.


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.