Delphi 7 IDE freezes when starting debugger (WinXP SP2) HELP!
Udo Giacomozzi
I waited a long time before I installed SP2 for WinXP but now I did and
Delphi refuses to work properly.
Whenever I start a program with the internal debugger activated, the IDE
freezes completely and the program does not even get started. Without
debugger all works fine. No matter what program I try.
I already re-installed Delphi completely without luck. Also tried with the
7.1 update (btw, is it normal that the About box reports the same build
number?)
I know I could uninstall SP2 but I am afraid that would make even more
problems as some Patches have been installed in the meantime...
A search with Google reported only issues with RC1 of the SP, but I seem to
be the only one that has problems with the final release.
Please help!!
Delphi 7 Enterprise (German edition)
Windows XP (German)
Service Pack 2 installed 2005/02/05
Windows Update active (so all patches installed)
Udo
Liz
> I already re-installed Delphi completely without luck. Also tried
> with the 7.1 update (btw, is it normal that the About box reports the
> same build number?)
It should say 8.1
> I know I could uninstall SP2 but I am afraid that would make even
> more problems as some Patches have been installed in the meantime...
I have SP2, and my delphi 7 and its debugger is working fine.
have you checked that the delphi debugger is in fact the current JIT
debugger?
Udo Giacomozzi
@newsgroups.borland.com:
> It should say 8.1
Why? It's Delphi 7 and I mean the update released 05/28/2004, see
http://www.borland.com/products/downloads/registered/download_delphi.html
>
>> I know I could uninstall SP2 but I am afraid that would make even
>> more problems as some Patches have been installed in the meantime...
>
> I have SP2, and my delphi 7 and its debugger is working fine.
>
> have you checked that the delphi debugger is in fact the current JIT
> debugger?
Where can I check that? I thought Delphi will check that on each startup.
And, doesn't the JIT affect only applications that run outside the IDE?
Thanks,
Udo
Liz
> Why? It's Delphi 7 and I mean the update released 05/28/2004, see
> http://www.borland.com/products/downloads/registered/download_delphi.h
> tml
The build number is 8.1 dont look at me, I dont work there.. See
screengrab in attachments.
> Where can I check that? I thought Delphi will check that on each
> startup. And, doesn't the JIT affect only applications that run
> outside the IDE?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\AeDebug\Debugger=C:\Program
Files\Borland\Delphi7\Bin\bordbg70.exe -aeargs %ld %ld
Udo Giacomozzi
news:421c...@newsgroups.borland.com:
> The build number is 8.1 dont look at me, I dont work there.. See
> screengrab in attachments.
Well, I made a screenshot of the "About" box before and after applying the
update. It remained the exactly the same. I already re-installed Delphi
completely and tried the patch again - same result. Right now I have the
third re-install running without the patch.
>
>> Where can I check that? I thought Delphi will check that on each
>> startup. And, doesn't the JIT affect only applications that run
>> outside the IDE?
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> NT\CurrentVersion\AeDebug\Debugger=C:\Program
> Files\Borland\Delphi7\Bin\bordbg70.exe -aeargs %ld %ld
Yes, there is this registery key with the correct value.
Any idea?
Udo
Liz
> Well, I made a screenshot of the "About" box before and after
> applying the update. It remained the exactly the same. I already
> re-installed Delphi completely and tried the patch again - same
> result. Right now I have the third re-install running without the
> patch.
Does your version say Version 7.0 (Build 8.1)?
> Yes, there is this registery key with the correct value.
>
> Any idea?
Are you by any chance working on a remote network? or, have lots of
paths to remote networks??
networks being inherantly slower than local drives may cause issues if
they dont respond quickly enough or you have lots of remote paths...
Udo Giacomozzi
@newsgroups.borland.com:
> Does your version say Version 7.0 (Build 8.1)?
No, it says:
Borland Delphi Enterprise
Version 7.0 (Build 4.453)
This keeps the same after installing the 7.1 update. The update itself
terminates successfully but afterwards the compiler complains about unit
SqlConst been built with a different referenced unit...
> Are you by any chance working on a remote network? or, have lots of
> paths to remote networks??
Yes, local network with 4 connected drive letters. But I work locally.
Also, that has never been a problem before...
> networks being inherantly slower than local drives may cause issues if
> they dont respond quickly enough or you have lots of remote paths...
No, we use CVS. All project files are stored locally.
One thing is strange: I just worked on a console application with the
internal debugger disabled. The app crashed (forced Windows to terminate
the task) and then an AV happened in some Borland Debugger DLL (can't
remember the file name). The message was displayed inside the Delphi IDE.
No idea why this could happen since the debugger is disabled and I didn't
use the JITD.
This is driving me crazy
Udo
Achim Kalwa
Liz wrote:
> Udo Giacomozzi wrote:
>
>>I already re-installed Delphi completely without luck. Also tried
>>with the 7.1 update (btw, is it normal that the About box reports the
>>same build number?)
>
> It should say 8.1
It should, but it does not. In international versions, Borland missed to
update the resource file (delphi32.de or delphi32.fr), which contains
the version number. I've reported this issue in QC last year:
http://qc.borland.com/wc/qcmain.aspx?d=8122
<quote>
Resolution: Won't Do
Resolved in Build: 9.0.1761.24408
</quote>
Achim
Liz
> It should, but it does not. In international versions, Borland missed
> to update the resource file (delphi32.de or delphi32.fr), which
> contains the version number. I've reported this issue in QC last year:
>
> http://qc.borland.com/wc/qcmain.aspx?d=8122
>
> <quote>
> Resolution: Won't Do
> Resolved in Build: 9.0.1761.24408
> </quote>
Boo Hiss.
Liz
> This keeps the same after installing the 7.1 update. The update
> itself terminates successfully but afterwards the compiler complains
> about unit SqlConst been built with a different referenced unit...
Sure you dont have more than one copy of the dcu?
> One thing is strange: I just worked on a console application with the
> internal debugger disabled. The app crashed (forced Windows to
> terminate the task) and then an AV happened in some Borland Debugger
> DLL (can't remember the file name). The message was displayed inside
> the Delphi IDE. No idea why this could happen since the debugger is
> disabled and I didn't use the JITD.
Explorer if you enable the JIT debugger in IE, will auto try and debug
it sometimes.. PITA :(
Udo Giacomozzi
@newsgroups.borland.com:
> Udo Giacomozzi wrote:
>
>> This keeps the same after installing the 7.1 update. The update
>> itself terminates successfully but afterwards the compiler complains
>> about unit SqlConst been built with a different referenced unit...
>
> Sure you dont have more than one copy of the dcu?
It's a standard Unit AFAIK and I reinstalled Delphi without installing any
3rd party packages...
Udo
Udo Giacomozzi
@newsgroups.borland.com:
> Explorer if you enable the JIT debugger in IE, will auto try and debug
> it sometimes.. PITA :(
Now I uninstalled Delphi, removed the remaining files and installed it
again. No luck.
However, I found a file named BORdbg70.31C.log in the "bin" directory that
contains these lines:
[E68:3E73] StartServiceCtrlDispatcher being called.
[E68:3E73] StartServiceCtrlDispatcher failed.
[E68:3E73] StartServiceCtrlDispatcher being called.
[E68:3E73] StartServiceCtrlDispatcher failed.
[E68:3E73] StartServiceCtrlDispatcher being called.
[E68:3E73] StartServiceCtrlDispatcher failed.
Somebody knows the meaning of this?
Udo
Liz
> Anyone has an idea what I could try now?
Getting any messages in your eventlog (the windows one not the delphi
one)?
Udo Giacomozzi
news:Xns96066781CAC3F...@207.105.83.66:
> Delphi 7 IDE freezes when starting debugger
I just deinstalled all Windows patches and the SP2 update, still Delphi
refuses to work with the debugger.
Anyone has an idea what I could try now?
Udo
Udo Giacomozzi
@newsgroups.borland.com:
I finally found the reason of all problems: It was the updated version of
my antivirus program, F-Secure. The originally installed version worked
fine with delphi, but not the newest. Of course I tried to disable the AV
as part of my tests but that didn't help. Who thinks that you actually have
to *deinstall* the AV to really disable it?
Anyway, thanks for your help. Will see if I can make F-Secure work with
Delphi...
Udo