Re: Deadlock with Single Threaded Application

From:

"Alexander Grigoriev" <alegr@earthlink.net>

Newsgroups:

comp.programming.threads,microsoft.public.vc.mfc,microsoft.public.vc.language,microsoft.public.vstudio.development

Date:

Sat, 14 Jul 2007 12:03:23 -0700

Message-ID:

<#BMzmmkxHHA.4588@TK2MSFTNGP05.phx.gbl>

To set a breakpoint, the debugger has to stop (break) the process.
The debugger is trying to do break first, to interrupt the process at well
known good point, such as system call. If it's not able to do break in a
reasonable time, it just suspends the process (does what it calls break, but
I would call it hard break).

"PeterOut" <MajorSetback@excite.com> wrote in message
news:1184425235.110093.28500@g4g2000hsf.googlegroups.com...

I am using MS Visual C++ 6.0 (Professional edition) on Win XP 5.1 SP
2.

I am developing a Windows application that calls vanilla C/C++
classes. I have gone to
Project:Settings:C/C++:Code Generation
and selected
Debug Single-Threaded
under
Use Run-Time Library

Despite the fact that I use exactly the same code every time, the
program sometimes runs through to completeion w/o any problems and
sometimes hangs in random places. Both of these outcomes occurs both
when I am doing other work on the PC and when I leave the PC with a
single application running. I know that it is hanging when it is
still running long after it usually completes. When I do a
Debug: Break
it is on some random (except usually string related) operation. I set
a breakpoint on the very next line and call Go (F5) but it never gets
there. The output gives me the error message:
BG: Break command failed within 3 seconds.
DBG: Potential deadlock. Soft broken.

OK, so how do I get this with a single-threaded application?

Many thanks in advance for any help,
Peter.