On Tue, 2006-03-14 at 00:53 -0700, dennis wrote: > Ross Johnson wrote: > > >gdb /etc/openoffice.org-2.0/program/soffice.bin > > > >and then type 'run' <Enter>. > > > >When it segfaults, type 'where' <Enter>. > > > >I don't think there are any debugging symbols in OOo but it just may > >indicate which module or library etc the segfault occurs in. > > > > > > I haven't had Open Office on this install before, but the previous > install I definitely had the 1.x series of OO and its my same home > directory. However...I just ran openoffice from gdb as you suggested and > guess what? It didn't fail. It took me through entering my name and all > that and now it runs fine just by running /usr/bin/soffice. > > Not sure what else to say. It works now, but why oh why did it taking > running gdb to make it work?
Applications that segfault often run in a debugger when they fail otherwise. It has to do with the way the debugger changes the execution environment, like memory allocation etc. I did not expect that to happen of course. I suspect that having OOo run once it has overwritten or created whatever it was that indirectly led to the segfault. probably in your OOo user profile. Did you request OOo to transfer previous user data at some point? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
