[Libreoffice] minutes of tech. steering call ...
Michael Stahl
mstahl at redhat.com
Fri Nov 25 02:20:50 PST 2011
On 24/11/11 21:23, Caolán McNamara wrote:
> On Thu, 2011-11-24 at 16:26 +0000, Michael Meeks wrote:
>> + subsequentcheck
>> + number of ways to improve it (Caolan)
the way i've always debugged it is something like:
DISPLAY=:42 ./soffice "--accept=pipe,name=$USER;urp;" --norestore
--nologo -env:UserInstallation=file:///tmp/xyz
then attach gdb to soffice.bin
then run subsequenttests e.g.
make subsequentcheck OOO_TEST_SOFFICE="connect:pipe,name=$USER"
can run this in a loop as well...
>> + Bjoern has a nice write-up of how to debug it here:
>
> i.e. sommat like
> a) just move that out of dev-tools into bin or solenv/bin
> b) tweak it to honour $COLORTERM/$TERM -e
> c) add a handle SIGPIPE nostop noprint pass
> d) get the definitely correct pid in there
> ---
> e) get the tooling to catch the disconnected error and say that
> LibreOffice crashed, rather than the current somewhat obscure error
> f) spit out a line liner to rerun the first failing test in isolation
> with soffice server under gdb
this would of course be very useful when running the tests
non-interactively such as on tinderboxes.
More information about the LibreOffice
mailing list