Re: failed unit test: sal_osl_file

On Thu, 2012-05-10 at 16:18 +0100, Caolán McNamara wrote:
> On Wed, 2012-05-09 at 17:17 -0400, Terrence Enger wrote:
> > I am trying to build master commit id 5c2c0e3, pulled 2012-05-08, on
> > ubuntu-natty (11.04), and it is failing in unit test sal_osl_file.
>
> You didn't flip from a system cppunit to an internal one without a
> rebuild inbetween, or anything like that ?


I think not.  But my system does have ubuntu-supplied
libcppunit.  Could a change in the build system since my
previous successful build (2012-04-01) have done this
silently?  My autogen.lastrun was last changed 2012-03-09,
and it shows no reference to cppunit:

    --disable-mozilla
    --enable-symbols
    --enable-dbgutil
    --enable-crashdump
    --disable-build-mozilla
    --without-system-postgresql
    --enable-python=internal

Moreover, the error looks the same after `make clean`.


Meanwhile, I applied a blunt instrument to the failing
testcase.  This lets the build progress to CUT sal_osl_module.
This unit test fails in SAL_INFO at module.cxx:321, which
leads to "free: invalid pointer" and SIGABRT.  One must
suspect a problem between the system-supplied stream
functions and the LO-supplied custom allocator, but to trace
through that is beyond my skill level.  (If I were smarter,
I would have given up sooner.  Sigh!)


gdb, of course, eats the return code from a failed unit
test.  So I can go on to see four more unit tests fail with
"free(): invalid pointer" after one of the "message" macros.



Thank you for your patience.
Terry.