Hi Mathias,
This is how I ran configure:
./configure
--with-frame-home=/cygdrive/c/MS_Visual_Studio.NET_2003/SDK/v1.1
--with-jdk-home=/cygdrive/c/j2sdk1
-disable-directx --with-ant-home=/cygdrive/c/apache-ant-1.6.2
--with-nsis-path=/cygdrive/c/NSIS --with-use-shel
with-num-cpus=2 --with-lang="he" --with-dict=HE_IL,EN_US --enable-dbgutil
Then I "source"d the resulting winenv.set, and ran dmake.
I've used this build many times in the past, and it's worked fine. Today
was the first time that I changed the trace setting to "debugger", and
that is what triggered the problem.
Alan
Mathias Bauer wrote:
Alan Yaniger wrote:
Hi list-memebers,
I've built a Windows version which enables the debug console, and which
I've been using productively. Today I opened the debug console, and
changed the setting for debug output of either "Trace" or "Warning" (I
don't remember which) to be directed to "Debugger". OOo then crashed.
When I try to restart OOo, I get the document recovery screen, with no
documents in the recover list. Pressing the OK button just gives me the
same screen, so I can't get into OOo. I'm stuck. I've tried uninstalling
and reinstalling, manually deleting the "Documents and
Settings/xxx/Application Data/OpenOffice.org2" directory and "Program
Files/OpenOffice.org" directory, going through the Windows registry and
manually deleting all keys and values that refer to the directory of
this installation of OOo. Nothing works. I am able to open non-debug
versions of OOo on my disk, but not my debug version. Can someone help out?
By deleting the user data you should have solved the problem of
autorecovery starting each time when you start OOo.
Obviously your "debug version" still crashes when you start it, is that
correct? How exactly did you build that version?
Best regards,
Mathias
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
