RE:Strange debugging problem

This kind of problem is generally caused by having an
expression in a watch list that invokes some code
in your app that sometimes behaves oddly (e.g., hangs).
Whenever dev studio hits a breakpoint or for any other
reason 'returns to the debugger after executing app code'
it re-evaluates all the expressions in your watch lists, even
the ones you aren't currently viewing.  This can cause
really mysterious and frustrating behaviour :).  The answer
is 'clear your watch lists when this happens'.

Kevin Wasserman
Mad Doc Software

>From: [email protected]
>Reply-To: [email protected]
>To: [email protected]
>Subject: Gamedevlists-windows digest, Vol 1 #385 - 2 msgs
>Date: Mon, 20 Feb 2006 20:07:41 -0800
>
>Send Gamedevlists-windows mailing list submissions to
>	[email protected]
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
>or, via email, send a message with subject or body 'help' to
>	[email protected]
>
>You can reach the person managing the list at
>	[email protected]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Gamedevlists-windows digest..."
>
>
>Today's Topics:
>
>    1. strange debugging problem (Andras Balogh)
>    2. Re: strange debugging problem (Martin Slater)
>
>--__--__--
>
>Message: 1
>Date: Mon, 20 Feb 2006 19:00:07 -0700
>From: "Andras Balogh" <[email protected]>
>To: [email protected]
>Subject: [GD-Windows] strange debugging problem
>Reply-To: [email protected]
>
>While my application is running, I can use alt-tab to switch to other
>programs and then switch back, and all this seems to work fine. However,
>when I switch to Visual Studio, and put a breakpoint in the source, while
>the program is running under the debugger, the program just.. well.. I
>don't know how to describe it, it kinda hangs, but it does this in a very
>strange way. The VS debugger says it's still running, but when I try to
>break into it (using the break all command that should just stop at the
>current instruction, wherever it is), it can't. The callstack window does
>not respond anymore, and I can not continue, or step anymore.. The only
>button on VS that works is the stop debugging. And it's funny, but when I
>say stop, I can actually see a couple more messages in the debug output
>window that my program is writing out..
>
>Anyone experienced anything like this? Any ideas about what might cause
>it, and possible workarounds?
>
>This is on VC++ 7.1 /Win32 XP
>
>
>thx,
>
>Andras




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Gamedevlists-windows mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
Archives:
http://sourceforge.net/mailarchive/forum.php?forum_id=555