Bug#176045: openoffice.org: Memory Access Fault for user setup

[Chris Halls <halls@debian.org>]

severity 176045 important
tags 176045 + unreproduceable
tags 176045 + moreinfo
thanks

On Fri, Jan 10, 2003 at 11:29:07AM +0100, Chris Halls wrote:
> Hi, can you see if you can get setup to generate a coredump to send to me?

I've still not heard back about this bug.  There is a new upstream release
in unstable now - please will you test if this still happens?

I have rewritten the section about crashes in README.Debian - here is what
to do if you still have crashes:
----------------------------
3.  You may be able to provide us with information about the crash by producing
a core dump.  Make sure you are in a directory where you have write permission,
and execute this:

  ulimit -c 10000; LD_LIBRARY_PATH=/usr/lib/openoffice/program /usr/lib/openoffice/program/setup.bin -R:/etc/openoffice/autoresponse.conf

When setup crashes, you should see the message 'Segmentation fault (core
dumped)'. and find a file named 'core' in your working directory.  Examine it
in gdb with these commands:

  echo where > gdb.script
  gdb /usr/lib/openoffice/program/setup.bin core < gdb.script | tee openoffice.log

Now you have a backtrace of the crash in the file 'openoffice.log', which will
indicate what the problem could be - please check the open bug reports, and if
there is no similar report, file a new report and attach the openoffice.log
file.  We may ask you to send your 'core' file if the crash is unknown to us.
----------------------------

Please mail the 'openoffice.org' log of your crash to this bugreport.

Thanks,
Chris