Re: [Libreoffice] MacOs Build failure in: unit test #2 on library ../../unxmacxi.pro/lib/libswdoctest.dylib

On Fri, Jan 28, 2011 at 3:39 AM, Caolán McNamara <caolanm@redhat.com> wrote:
> On Thu, 2011-01-27 at 15:21 -0600, Norbert Thiebaud wrote:
> > ----------------------------------------------------------
> > - start unit test #2 on library ../../unxmacxi.pro/lib/libswdoctest.dylib
> > ----------------------------------------------------------
> > /bin/sh: line 1: 85233 Bus error
>
> So, can we get any debugging info for that, i.e. get gdb in there
>
> e.g. export GDBCPPUNITTRACE="gdb --args" and run dmake in the afflicted
> dir.

(gdb) run
Starting program:
/Volumes/Raid0/tb/solver/330/unxmacxi.pro/bin/cppunittester
../../unxmacxi.pro/lib/libswdoctest.dylib -headless -invisible
-env:UNO_SERVICES=file:///Volumes/Raid0/tb/clone/writer/sw/qa/core/../../unxmacxi.pro/misc/test-bigptrarray/services.rdb
-env:UNO_TYPES=file:///Volumes/Raid0/tb/clone/writer/sw/qa/core/../../unxmacxi.pro/misc/test-bigptrarray/types.rdb\
file:///Volumes/Raid0/tb/clone/writer/sw/qa/core/../../unxmacxi.pro/misc/test-bigptrarray/udkapi.rdb
-env:OOO_BASE_DIR=file:///Volumes/Raid0/tb/clone/writer/sw/qa/core/../../unxmacxi.pro/misc/test-bigptrarray
-env:BRAND_BASE_DIR=file:///Volumes/Raid0/tb/clone/writer/sw/qa/core/../../unxmacxi.pro/misc/test-bigptrarray
-env:UNO_USER_PACKAGES_CACHE=file:///Volumes/Raid0/tb/clone/writer/sw/qa/core/../../unxmacxi.pro/misc/test-bigptrarray
Reading symbols for shared libraries
.+++++...........................................................................................
done
Reading symbols for shared libraries
............................................ done
Reading symbols for shared libraries ... done
Reading symbols for shared libraries . done
Reading symbols for shared libraries . done
Reading symbols for shared libraries .. done
Reading symbols for shared libraries . done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000014
0x06c91710 in ResMgr::GetResource ()
(gdb) bt
#0  0x06c91710 in ResMgr::GetResource ()
#1  0x06c8c658 in Resource::GetRes ()
#2  0x03fe53a7 in ShellResource::ShellResource ()
#3  0x03fe642b in _InitUI ()
#4  0x0380a61b in SwDLL::Init ()
#5  0x03804d18 in SwDocTest::SwDocTest ()
#6  0x03807e52 in CppUnit::ConcretTestFixtureFactory<SwDocTest>::makeFixture ()
#7  0x00025f2d in CppUnit::TestSuiteBuilderContextBase::makeTestFixture ()
#8  0x03808081 in SwDocTest::addTestsToSuite ()
#9  0x03808c55 in CppUnit::TestSuiteFactory<SwDocTest>::makeTest ()
#10 0x0001829d in CppUnit::TestFactoryRegistry::addTestToSuite ()
#11 0x00018346 in CppUnit::TestFactoryRegistry::makeTest ()
#12 0x0000294e in main ()

> I *imagine* that seeing as the writer test is in there a few weeks now
> that it used to pass, and that this has recently stopped working.

yes it _has_ worked, I'd say a week or so ago

Norbert

> C.