Bug 55302 - FILEOPEN CRASH SIGSEGV on a particular embedded hsqldb file
Summary: FILEOPEN CRASH SIGSEGV on a particular embedded hsqldb file
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
4.0.0.0.alpha0+ Master
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks: 37641
  Show dependency treegraph
 
Reported: 2012-09-25 03:12 UTC by Terrence Enger
Modified: 2012-10-02 03:18 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
typescript of gdb session with backtrace (81.74 KB, text/plain)
2012-09-25 03:12 UTC, Terrence Enger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Terrence Enger 2012-09-25 03:12:53 UTC
Created attachment 67660 [details]
typescript of gdb session with backtrace

When LibreOffice built from master attempts to open the file attached
to fdo#37641 "By using Rowset I get not full output", it gets a SIGSEGV
before (or, without?) presenting dialog box asking "enable macros?".
The attached typescript has `thread apply all backtrace full` starting
at line 75.

Note for comparison that LibreOffice supplied with ubuntu natty, 
    LibreOffice 3.3.4 
    OOO330m19 (Build:401)
    tag libreoffice-3.3.3.1, Ubuntu package 1:3.3.4-0ubuntu1.4
opens the file without crashing, and I can display data.

The failing LibreOffice is commit 66e33e2, pulled 2012-09-17 and
configured with ...
    --enable-symbols
    --enable-dbgutil
    --enable-crashdump
    --disable-build-mozilla
    --without-system-postgresql
    --enable-debug
    --enable-werror

The build and execution environment is ubuntu natty (11.04) set up for
use in English ...
    $ 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

Terry.
Comment 1 Terrence Enger 2012-10-02 03:18:52 UTC
With master cc1a112, pulled 2012-10-01, the problem is not evident in
the environment where I reported it originally.  Not being able to
point to a code change to account for the difference, I am setting
this bug WORKSFORME.