|
|
|
date: Tue, 12 Aug 2008 04:26:47 -0700 (PDT),
group: microsoft.public.vstudio.general
back
Re: Debugging unusable in SP1
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 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.
date: Tue, 12 Aug 2008 04:37:35 -0700 (PDT)
author: Oolis
Re: Debugging unusable in SP1
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" wrote in message
news:f644149a-2713-4aa8-ae5d-b89928c728d8@a70g2000hsh.googlegroups.com...
> 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 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.
>
date: Tue, 12 Aug 2008 09:29:00 -0400
author: John Saunders
RE: Debugging unusable in SP1
hi,
i found one more problem while in debug mode with SP1. when i disable the
breakpoints(NOT delete), it appears as the breakpoints are deleted. although
the breakpoints are still there, they are not shown like unfilled red circle
or hidden. when i open the breakpoint window, i can see the set breakpoints
which are now in the disable state. on enabling them from the breakpoint
window, they again start appering.
"Oolis" 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.
>
date: Tue, 14 Oct 2008 23:22:01 -0700
author: Rock
|
|