https://bugs.freedesktop.org/show_bug.cgi?id=65358

--- Comment #1 from Terrence Enger <[email protected]> ---
Created attachment 80573
  --> https://bugs.freedesktop.org/attachment.cgi?id=80573&action=edit
typescript two SIGSEGV's and gdb backtrace

I tried to reproduce this on Linux, but I did not get past step 3--or
maybe not even beyond step 2.

The right click in step 3 failed to display the pop-up menu.  I saw
that LibreOffice was pegging the CPU, and after 3 or 5 minutes of
this, I typed ctrl-C in the terminal.  Resulting error messages in the
terminal include a SIGSEGV in the Java Runtime and a SIGSEGV in
OUString::equals.

The present attachment includes a gdb backtrace from OUString::equals;
I shall soon attach the error report from the Java Runtime.

I am leaving bug status UNCOMFIRMED because it is not clear that my
crash is the same crash that the original reporter saw.


My LibreOffice is master 45abf35, pulled 2013-05-29, configured as

    --enable-option-checking
    --enable-dbgutil
    --enable-crashdump
    --disable-build-mozilla
    --without-system-postgresql
    --without-myspell-dicts
    --without-help
    --with-extra-buildid

built and running on ubuntu-natty (32-bit) 

    $ uname -a
    Linux cougar-natty 2.6.38-16-generic #67-Ubuntu SMP Thu Sep 6 18:00:43 UTC
2012 i686 athlon i386 GNU/Linux

    $ gcc --version
    gcc (Ubuntu/Linaro 4.5.2-8ubuntu4) 4.5.2
    Copyright (C) 2010 Free Software Foundation, Inc.
    This is free software; see the source for copying conditions.  There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

    $ java -version
    java version "1.6.0_24"
    OpenJDK Runtime Environment (IcedTea6 1.11.5)
(6b24-1.11.5-0ubuntu1~11.04.1)
    OpenJDK Client VM (build 20.0-b12, mixed mode, sharing)

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to