Re: Debugging unusable in SP1
- From: "John Saunders" <no@xxxxxxxxxxxxxxxx>
- Date: Tue, 12 Aug 2008 09:29:00 -0400
Try it with a "Hello, world" program with the Autos window displayed, and see if the problem still happens. If it does not, then the issue will be the Autos window when it's displaying your program, and I'd look for a recursive property or something like that.
--
John Saunders | MVP - Connected System Developer
"Oolis" <Oolis.Kraprin@xxxxxxxxxxxxxx> wrote in message news:f644149a-2713-4aa8-ae5d-b89928c728d8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Further info: Problem appears to be related to the Autos window. When.
this is displayed the problem occurs, when it is not displayed the
problem does not appear. Other windows such as the callstack or locals
do not cause the problem. When the Autos is active but hidden or auto
hidden (appears as a tab) the problem does not occur. When it is
floating the problem occurs.
On Aug 12, 1:26 pm, Oolis <Oolis.Krap...@xxxxxxxxxxxxxx> wrote:Hi,
just installed SP1 for .net 3.5 and vs 2008.
Now when I am debugging, devenv uses 100% cpu, and the text editor
window is inactive. So for example on breakpoints the code I am
stopped at is not displayed. Scrollbars can be adjusted but the text
shown in the text area is not updated, i can click on other tabs and
the tabs select. but the text area does not refresh. If I minimize the
window and maximize it again, the entire text area is grey.
Interestingly if I go to full-screen, it works normally in full
screen, but going back to normal the problem remains. This makes
debugging extremely difficult.
Any suggestions?
Oolis.
- References:
- Debugging unusable in SP1
- From: Oolis
- Re: Debugging unusable in SP1
- From: Oolis
- Debugging unusable in SP1
- Prev by Date: Re: Debugging unusable in SP1
- Next by Date: Re: transferring files with windows XP
- Previous by thread: Re: Debugging unusable in SP1
- Next by thread: VB.Net 2008 run project
- Index(es):
Relevant Pages
|