RE: debugger IDE hangs when stepping with properties in watch wind
From: asanford (asanford2000_at_hotmail.com)
Date: 11/14/04
- Next message: Anil Punjabi: "Debugging slowness"
- Previous message: Emil Astrom: "Re: Debugging classic ASP in VS.Net 2003"
- In reply to: Rhett Gong [MSFT]: "RE: debugger IDE hangs when stepping with properties in watch window"
- Next in thread: Rhett Gong [MSFT]: "RE: debugger IDE hangs when stepping with properties in watch wind"
- Reply: Rhett Gong [MSFT]: "RE: debugger IDE hangs when stepping with properties in watch wind"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 14 Nov 2004 08:39:01 -0800
Thanks - but as I'm typically changing context with each step (from one
thread or function to another), adding and then removing items from the watch
window before each step isn't really very helpful - basically, it's just like
using quickwatch. Watching actual variable members - instead of calculated
"properties" - is another workaround. But, I'm fairly certain the hang I'm
seeing isn't just "slow response" - I've left it there for around 10 minutes!
It is almost certainly a deadlock of some sort. Can microsoft please respond
with a verification that this a true bug (and a fix would be great!), or else
provide some rationale that they don't think it is a true bug (and so tell me
what I am doing wrong)?
"Rhett Gong [MSFT]" wrote:
> Hello,
> If you put local variables (e.g. object properties in your case) in the
> watch window, it will cost debugger much time to resolve these variables,
> when the context changes.
> In some situation, it will take debugger very long time to resolve these
> variables, like debugger hangs and may cause some unexpected behaviors.
> Since you put these variables in watch window ---- that means you want
> debugger to display value of these variables in any situation, but debugger
> is not that smart to know context changes, so it will try its best to
> resolve them for you.
> Personally, I prefer dv command of Windbg to check local, global,
> parameter, function, or unknown variables. For watch window in VS debugger,
> I think a better way to workaround this problem is to remove these
> variables from watch window before context changes.
>
>
> Best regards,
> Rhett Gong [MSFT]
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Please reply to newsgroups only. Thanks.
>
>
- Next message: Anil Punjabi: "Debugging slowness"
- Previous message: Emil Astrom: "Re: Debugging classic ASP in VS.Net 2003"
- In reply to: Rhett Gong [MSFT]: "RE: debugger IDE hangs when stepping with properties in watch window"
- Next in thread: Rhett Gong [MSFT]: "RE: debugger IDE hangs when stepping with properties in watch wind"
- Reply: Rhett Gong [MSFT]: "RE: debugger IDE hangs when stepping with properties in watch wind"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|