debugging open office

Trying to run the latest version of openoffice on my system (SuSE7.2), but it crashes when loading.  So, I figure I need to run a stack trace, but I'm getting nowhere in trying.  First, I tried to use gdb, but the 'soffice' executable is a shell script, and I can't see what it points to - there's a file called 'soffice.bin' but that doesn't help.  

Someone told me that if it's crashing it should create a core file, but I can't figure out how to go about accessing this.  Can someone point me in the right direction?
elsdonAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
ahoffmannConnect With a Mentor Commented:
soffice is a script, usually.
If not called remote, it starts a program soffice.bin in the installation directory, the line in the script looks like:
   exec "$sd_inst/program/$sd_binary" "$1" "$2" "$3" "$4" "$5" "$6" "$7" "$8" "$9"

I'm not shure about the open office version, but think it's very similar.

To start soffice.bin either prepend the call by gdb, or start gdb right after it with the PID of the running soffice.bin.

If you want tu run gdb with the core file, just pass it as argument (full path) to gdb.
Keep in mind that the soffice script cd to another directory, you probably find the core there.
Also keep in mind that your shell may restrict the generation of core files, see the limit or ulimit (depending on your shell) command.
0
All Courses

From novice to tech pro — start learning today.