468,248 Members | 1,470 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,248 developers. It's quick & easy.

exiting debug process

I'm using Visual C++ 6.0 on Windows 2000/XP machines. I can't run this
program in release mode because the libraries/dll are not compatiable
with release mode. I've looked for new ones and can't find them. My
problem is when I exit the program with the debug configuration
build(not while actually debugging the program) and only if it's still
processing data, if you go look in the task manager the process is
still running using all the memory and cpu as it was before I exited.
It is in a processor intensive loop(100%) and uses around 1 gb of
memory. This process never seems to end even after it should be
finished with the execution of the program.

Basically I'm just wondering, using an MFC app in debug configuration,
what could cause the program to not exit when exit was clicked? Is
there something I'm missing to cause it to kill the process on exit?
Thanks in advance for the help

Jan 24 '07 #1
7 1440

Also I forgot to mention, I KNOW this doesn't happen in release mode,
in release mode the process kills itself as expected. I have checked
all _DEBUG places and none of them cause it. I can tell release mode
does as expected because the dll/libraries needed don't happen until
much later in the process.

On Jan 24, 3:54 pm, tsmit...@gmail.com wrote:
I'm using Visual C++ 6.0 on Windows 2000/XP machines. I can't run this
program in release mode because the libraries/dll are not compatiable
with release mode. I've looked for new ones and can't find them. My
problem is when I exit the program with the debug configuration
build(not while actually debugging the program) and only if it's still
processing data, if you go look in the task manager the process is
still running using all the memory and cpu as it was before I exited.
It is in a processor intensive loop(100%) and uses around 1 gb of
memory. This process never seems to end even after it should be
finished with the execution of the program.

Basically I'm just wondering, using an MFC app in debug configuration,
what could cause the program to not exit when exit was clicked? Is
there something I'm missing to cause it to kill the process on exit?
Thanks in advance for the help
Jan 24 '07 #2
ts******@gmail.com wrote:
I'm using Visual C++ 6.0 on Windows 2000/XP machines. I can't run this
program in release mode because the libraries/dll are not compatiable
with release mode.
Then you're asking in the wrong place, try a VC specific group.

--
Ian Collins.
Jan 24 '07 #3
Just hoping I could get a little help if anybody knows teh answer

On Jan 24, 4:04 pm, Ian Collins <ian-n...@hotmail.comwrote:
tsmit...@gmail.com wrote:
I'm using Visual C++ 6.0 on Windows 2000/XP machines. I can't run this
program in release mode because the libraries/dll are not compatiable
with release mode. Then you're asking in the wrong place, try a VC specific group.

--
Ian Collins.
Jan 24 '07 #4
* ts******@gmail.com:
I'm using Visual C++ 6.0 on Windows 2000/XP machines. ... MFC app
Post to a Windows/Microsoft group; you're off-topic here.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
Jan 24 '07 #5
ts******@gmail.com wrote:

Top posting doesn't help your quest.
On Jan 24, 4:04 pm, Ian Collins <ian-n...@hotmail.comwrote:
>>tsmit...@gmail.com wrote:
>>>I'm using Visual C++ 6.0 on Windows 2000/XP machines. I can't run this
program in release mode because the libraries/dll are not compatiable
with release mode. Then you're asking in the wrong place, try a VC specific group.
Just hoping I could get a little help if anybody knows teh answer
The regulars of platform specific groups are better qualified to answer
questions specific to that platform.

They may well post here as well, but this group is specifically for
discussing C++ core language issues.

--
Ian Collins.
Jan 24 '07 #6
ts******@gmail.com wrote:
I'm using Visual C++ 6.0 on Windows 2000/XP machines. I can't run this
program in release mode because the libraries/dll are not compatiable
with release mode. I've looked for new ones and can't find them. My
problem is when I exit the program with the debug configuration
build(not while actually debugging the program) and only if it's still
processing data, if you go look in the task manager the process is
still running using all the memory and cpu as it was before I exited.
It is in a processor intensive loop(100%) and uses around 1 gb of
memory. This process never seems to end even after it should be
finished with the execution of the program.

Basically I'm just wondering, using an MFC app in debug configuration,
what could cause the program to not exit when exit was clicked? Is
there something I'm missing to cause it to kill the process on exit?
Thanks in advance for the help
If a program operates differently in debug mode and release mode it's
almost always because you have a bug in your code. Something like an
uninitialised variable. Could be anything really. When you have a bug
your program often ceases to behave in a logical manner, so looking 'in
all the _DEBUG places' is not likely to help much.

Try the usual debugging techniques.

John
Jan 24 '07 #7
John Harrison wrote:
ts******@gmail.com wrote:
>
Try the usual debugging techniques.
In this case I would try code elimination, i.e. try cutting out sections
of your code. The last piece of code you remove before the problem goes
away is likely to be where the problem lies (but there are no guarantees).
Jan 24 '07 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by Tim Clacy | last post: by
3 posts views Thread by Bonj | last post: by
5 posts views Thread by hzgt9b | last post: by
23 posts views Thread by Boltar | last post: by
reply views Thread by NPC403 | last post: by
reply views Thread by kermitthefrogpy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.