Bug 76174

Created attachment 95807 [details]
backtrace with symbols

Note frame 17:

#17 0x00007f77b9148cc3 in ImplDbgTestSolarMutex () at /home/terry/lo_hacking/git/libo4/vcl/source/app/dbggui.cxx:1624

The referenced function is:

1622: void ImplDbgTestSolarMutex()
1623: {
1624:     assert(ImplGetSVData()->mpDefInst->CheckYieldMutex());
1625: }

I am leaving the bug status UNCONFIRMED because I suspect that the
problem may be not widespread.  Well, obviously it can happen only in
a debug build, but even less widespread than that.  OTOH, developers
may be interested just because solar mutex is involved.  Advice
welcome.

FWIW, I see something similar when testing Firebird in my debug build :

warn:legacy.osl:22546:1:connectivity/source/drivers/firebird/DatabaseMetaData.cxx:1447: Not implemented yet!
warn:tools.debug:22546:1:tools/source/debug/debug.cxx:1121: no DbgTestSolarMutex function set

(In reply to comment #3)
> FWIW, I see something similar when testing Firebird in my debug build :
> 
> warn:legacy.osl:22546:1:connectivity/source/drivers/firebird/
> DatabaseMetaData.cxx:1447: Not implemented yet!
> warn:tools.debug:22546:1:tools/source/debug/debug.cxx:1121: no
> DbgTestSolarMutex function set

That's unrelated to Terrence's issue.  Here, the warning is because (presumably in an additional process besides soffice.bin?) the functionality has not been set up to detect potential violations of SolarMutex locking.  If you have a recipe to reproduce it, I can have a look to eliminate the warning.

(In reply to comment #4)

Hi Stephan,

> 
> That's unrelated to Terrence's issue.  Here, the warning is because
> (presumably in an additional process besides soffice.bin?) the functionality
> has not been set up to detect potential violations of SolarMutex locking. 
> If you have a recipe to reproduce it, I can have a look to eliminate the
> warning.

OK, will open another bug report for that. Easy to reproduce on my system.
Create an empty Firebird embedded db.
Add a table and/or data, e.g. by dragging and dropping from a Calc sheet.
Save, and close the Firebird ODB file.
 But, like I said, I will open a separate issue for this.


Alex

@Terrence : I don't get a crash with my debug master 440 build on OSX, with the document you indicated. Do you still get this ?

Created attachment 108117 [details]
backtrace from master 2014-10-14

Thank you, Alex, for the reminder.


The daily dbgutil bisect version 2014-10-20 and my dbgutil of master
commit 9d24f6b, fetched 2014-10-14, fail with a different assertion:

    soffice.bin: /home/terry/lo_hacking/git/libo4/vcl/source/app/dbggui.cxx:793: void ImplDbgTestSolarMutex(): Assertion `ImplGetSVData()->mpDefInst->CheckYieldMutex()' failed.

Attached backtrace is from my build.  I am *assuming* that this
information belongs here, but if it deserves a new bug report, I can
do that.

The daily dbgutil bisect version 2014-10-20 raises the same assertion.


I am setting bug status UNCONFIRMED.


My build is master commit 9d24f6b, fetched 2014-10-14 18:56 UTC,
configured:

    CXXFLAGS=-std=c++11 --enable-option-checking=fatal
    --enable-dbgutil --enable-crashdump --without-system-postgresql
    --without-myspell-dicts --with-extra-buildid --without-doxygen
    --with-external-tar=/home/terry/lo_hacking/git/src
    --disable-gstreamer --enable-gstreamer-0-10

built and running on debian-wheezy 64-bit.

The assertion is already present in daily dbgutil bibisect version
oldest (of course: the bug report is older than the repository), and
other bibisect repositories have product builds.  Setting whiteboard
notBibisectable.

Even though the backtrace has changed, this will only ever have happened on a dbgutil build so I think it's fine to go with the latest master backtrace. If it turns out there's another assert still hiding under the latest one, that can be dealt with later.

I can reproduce the latter backtrace with current master on both Linux and OSX, so setting -> NEW and Platform: All

Adding self to CC if not already on