Re: [GD-General] problems while debugger is attached

[Stefan B. <Ste...@di...>]

   I've seen this many times.
=20
   On Windows, the kernel will detect when you have a debugger attached =
and force the use of debug mode on heaps even if you're using the =
non-debug CRT. This will cause subtle differences in behaviour depending =
on what your (faulty) code looks like. There will be differences both in =
timing and memory contents / alignment.
=20
/Stefan

________________________________

From: gam...@li... on behalf of =
Andras Balogh
Sent: Sun 23/07/2006 21:49
To: gam...@li...
Subject: [GD-General] problems while debugger is attached



I have a strange bug, where if I'm running the program without the=20
debugger attached (CTRL-F5 in VS), the program would run correctly both =
in=20
debug and release builds. But when I run the program with F5, so the=20
debugger is attached, then it blocks on a function call and never =
returns.=20
If I put a breakpoint before this call, and step through it, then=20
everything seems to work fine, and the function returns as expected..

Could this be a deadlocking problem? Any ideas why attaching a debugger=20
makes any difference? And hints on how to debug this?

Thanks,



Andras

-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Gamedevlists-general mailing list
Gam...@li...
https://lists.sourceforge.net/lists/listinfo/gamedevlists-general
Archives:
http://sourceforge.net/mailarchive/forum.php?forum_id=3D557