Bug#234044: openoffice.org-bin: Segmentation fault

[Peter Luciak <peter@luciak.org>]

On Tue, Feb 24, 2004 at 12:33:57AM +0100, Chris Halls wrote:
> Please try to provide logs of what you are doing and seeing on the
> screen in addition to (or instead of) summarising in your own words; it
> helps me understand what exactly you have done, and the responses you
> received.

	Sorry. What I meant was:

avalon:c:~$ cd /usr/lib/openoffice/program; LD_LIBRARY_PATH=. strace ./setup.bin 2>&1 | grep -i "open(.*ttf" | tail
avalon:c:/usr/lib/openoffice/program$

> Is there anything created under ~/.openoffice before the segfault?  If
> so you might find setup.log - if so please post it since it may provide
> a clue to which stage the segfault occured.

	No, ~/.openoffice isn't even created. I also tried creating a new
user account and running openoffice -- with the same segfault.

> Does the same segfault happen if you run /usr/lib/openoffice/setup
> directly?

	Yes.

> cd /usr/lib/openoffice/program; LD_LIBRARY_PATH=/usr/lib/openoffice/program gdb ./setup.bin
> 
> Then type 'run' at the (gdb) prompt, wait for the crash and enter
> 'thread apply all bt full' at the next prompt.

(gdb) run
Starting program: /usr/lib/openoffice/program/setup.bin
(no debugging symbols found)...warning: shared library handler failed to enable breakpoint

Program received signal SIGSEGV, Segmentation fault.
0x4000a0a8 in ?? ()
(gdb) thread apply all bt full
(gdb)


bye
P.
-- 
Peter `cuco' Luciak             ICQ: 177414624
peter@luciak.org                jabber://cuc0@jabber.sk

The words 'gullible' and 'stupid' are no longer listed in dictionaries.
Go and look for yourself.