• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1684
  • Last Modified:

Debug process already running

When testing new code that has problems, sometimes I cannot break out of debug mode.  I get a message saying "Debug process already running" - when the process already running is the one I am trying to "kill".  Usually at this point I have to reboot.  I cannot close Delphi normally, I cannot kill the process through Ctrl+Alt+Delete.

I don't know if this behavior is normal for the debugger.  My expectations are, if I am running the program inside the IDE, then this means the program is running in a protected shell inside the IDE...and nothing the program does should be fatal to the OS - to the point I have to reboot.  

Am I dead wrong?

Thanks,

Tom
0
Tom Knowlton
Asked:
Tom Knowlton
1 Solution
 
jeurkCommented:
Hi,
Try to kill the program again when the dialog is open, normally the program will be killed about 10 seconds later.
At least this what is happening for me.
John.
0
 
Tom KnowltonWeb developerAuthor Commented:
I've tried waiting it out...no luck.
0
 
kretzschmarCommented:
did u tried

the program reset menu entry in the ide under the project menu before closing the ide
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Tom KnowltonWeb developerAuthor Commented:
Yes, I tried that.
0
 
jeurkCommented:
try switching to windows 2k or windows me or NT...
what's your OS ?
0
 
Tom KnowltonWeb developerAuthor Commented:
OS is Windows 98 SE.
0
 
jeurkCommented:
So, this could be the reason... 98 is not very good at killing processes, even not at managing processes...
Sorry, there is no solution under 98 I think...
0
 
Tom KnowltonWeb developerAuthor Commented:
You are saying that many of these problems that crash Delphi under Windows 98 are handled better by 2000, NT, Me, etc.?
0
 
MannSoftCommented:
Win2k is definately much better to use in a programming enviroment.  Here is what Ive found:

With Win98 when my programs crashed more often than not they would cause endless blue screens and I would be forced to reboot.  Occasionally I would be able to use CTRL-ALT-DEL to end the task but Delphi didnt appear to like that.  I would always have to close and reopen it before continuing (almost as annoying as restarting!).

With Win2k when my programs crash I can usually just use Program Reset and all is well.  There have been occasions where I have to CTRL-ALT-DEL them but again all is usually well.  But there have been rare occasions where I CTRL-ALT-DEL the application and when I try to recompile it Delphi says the EXE is still in use.  

So while Win2k is much better, it isnt going to solve 100% of your problems.  So your answer is of course, dont write programs that crash! :-)
0
 
Tom KnowltonWeb developerAuthor Commented:
MannSoft:

"Don't write programs that crash"

oh, I wish I wish I wish I could.  :)
0
 
jeurkCommented:
I will never accept coding again under 95 98 or even NT...
I would say that win2k will solve all your problems.
I never have to shut down the system again with win2K - NEVER.
The system is stable and does all I want.
That's what I think.
John.
0
 
Tom KnowltonWeb developerAuthor Commented:
Thanks MannSoft.

Thanks everyone.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now