7.1 IDE bug

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Daniel =?iso-8859-1?Q?Lidstr=F6m?= - 05 Nov 2004 09:21 GMT

Hi,

I have about 20 source files open when I start a debug session. Then all of
them are closed! Why is that?? Very annonying. Project is C++, not managed.
7.1.3088.

Signature

Daniel

Reply to this Message

Rudy Ray Moore - 05 Nov 2004 18:11 GMT

I don't have that problem. But sometimes when I start debugging, my
dockable windows move to the other side of the screen. I don't fight it
anymore. :(

Rudy

> Hi,
>
[quoted text clipped - 3 lines]
> managed.
> 7.1.3088.

Reply to this Message

Carl Daniel [VC++ MVP] - 05 Nov 2004 20:35 GMT

> I don't have that problem. But sometimes when I start debugging, my
> dockable windows move to the other side of the screen. I don't fight
> it anymore. :(

Keep in mind that the IDE maintains two completeely different window
layouts - one is used when the debugger is active, the other is used when
the debugger is inactive. There's nothing in the IDE that forces these
window layouts to be at all similar. You generally need to arrange the
windows separately for the two modes, but once you've done it once the
settings should "stick".

-cd

Reply to this Message

Julie - 10 Nov 2004 20:02 GMT

> > I don't have that problem. But sometimes when I start debugging, my
> > dockable windows move to the other side of the screen. I don't fight
[quoted text clipped - 8 lines]
>
> -cd

Microsoft, take *NOTE* -- this should be a configurable *OPTION*!!!

Reply to this Message

Tarek Madkour [MSFT] - 10 Nov 2004 20:19 GMT

>> Keep in mind that the IDE maintains two completeely different
>> window layouts - one is used when the debugger is active, the
[quoted text clipped - 6 lines]
> Microsoft, take *NOTE* -- this should be a configurable
> *OPTION*!!!

I'm not sure that this would be a useful option if we did expose
it as an option. My thinking is that I'm normally not interested
in cluttering my editor UI with process, breakpoint, threads,
modules, callstack, watch, autos, memory and similar windows when
I'm not debugging. I only want to see them when I'm debugging and
hence would need to specify a "debugger view" that's different
from my "editor view".

Thanks,

Signature

Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.

Reply to this Message

Julie - 10 Nov 2004 20:58 GMT

> >> Keep in mind that the IDE maintains two completeely different
> >> window layouts - one is used when the debugger is active, the
[quoted text clipped - 14 lines]
> hence would need to specify a "debugger view" that's different
> from my "editor view".

Ahhh, right. My head was in a box.

I was thinking of the solution explorer, property, etc. windows that I use in
both develop and debug views. Forgot about the other debug windows.

Reply to this Message

Hendrik Schober - 09 Nov 2004 13:24 GMT

Daniel Lidstr?m <someone@microsoft.com> wrote:

> Hi,
>
> I have about 20 source files open when I start a debug session. Then all of
> them are closed! Why is that?? Very annonying. Project is C++, not managed.
> 7.1.3088.

I've seen something similar.
I haven't been able to find a pattern
in this and cannot reproduce it. Just
that once in a while the IDE will close
some/most of the open files when I end
a debug session.
And yes, it annoys me to no end.

Schobi

Signature

SpamTrap@gmx.de is never read
I'm Schobi at suespammers dot org

"The presence of those seeking the truth is infinitely
to be prefered to those thinking they've found it."
Terry Pratchett

Reply to this Message

Tarek Madkour [MSFT] - 09 Nov 2004 18:02 GMT

>> I have about 20 source files open when I start a debug session. Then
>> all of them are closed! Why is that?? Very annonying. Project is C++,
[quoted text clipped - 7 lines]
> a debug session.
> And yes, it annoys me to no end.

This is not a bug that we have seen in our labs. Please let us know if
you are ever able to find some pattern to when this happens. We
certainly want to fix this bug.

Also, does it close all files, even unsaved ones? Does it save them?

Thanks,

Signature

Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.

Reply to this Message

Hendrik Schober - 10 Nov 2004 09:26 GMT

> [...]
>
[quoted text clipped - 13 lines]
>
> Also, does it close all files, even unsaved ones? Does it save them?

That's at the end of debug sessions. I
rarely ever have unsaved files then and I
certainly haven't seen a case where it
closed one of those.
I don't think it ever closed /all/ open
files, although I did see cases where I
was left with two or three open files when
I had more than a dozen of files open when
I stopped debugging.

I see this since I work with VC7.1 and it
happens like once in a months. (At least,
that's how often I realize it. There might
be cases where it closes files that I don't
miss afterwards.) In all the time I haven't
seen any pattern in when it does that.
However, now that I think of it, I remember
that the IDE also often forgets open files
after I get a newer version of some project
file in the solution from our source control
system. (Or does it do this all the time
then? I'm not sure.) Then, after opening the
solution, no file is open at all.

Sorry to be so vague.

> Thanks,

Schobi

Signature

SpamTrap@gmx.de is never read
I'm Schobi at suespammers dot org

"The presence of those seeking the truth is infinitely
to be prefered to those thinking they've found it."
Terry Pratchett

Reply to this Message

H Gohel - 10 Nov 2004 19:30 GMT

> >> I have about 20 source files open when I start a debug session. Then
> >> all of them are closed! Why is that?? Very annonying. Project is C++,
[quoted text clipped - 5 lines]
>
> Also, does it close all files, even unsaved ones? Does it save them?

This happens to me (and a few coworkers) as well. In our work environment,
we use the Visual Studio .NET 2003 Professional IDE, but with the Visual
Studio .NET (2002) Professional compilers by modifying the paths.

When I start debugging, the files are always saved anyway, so losing edits
is not an issue. But if during debugging the IDE opens new files and the
number of open files gets to a certain point, then the files from the very
left side (earliest opened) start to close by themselves as newer files are
opened. When the session ends, the files that were closed do not get
reopened (in case that was the intended behavior?).

This is especially annoying because the files on the very left are usually
the ones that I am currently editing/debugging. I have to go into solution
explorer, find and re-open them.

Signature

Himanshu

Reply to this Message

Tarek Madkour [MSFT] - 10 Nov 2004 20:16 GMT

This is a bad bug. Can you log the issue in the product feedback
center (http://lab.msdn.microsoft.com/productfeedback/) ?

This would be the best way to start investigating this bug and keep
the person investigating the bug in direct communication with those
who see it (you and others on the thread) in order to provide us with
more information as needed.

Thanks

Signature

Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.

Reply to this Message

Hendrik Schober - 11 Nov 2004 11:34 GMT

> [...]
>
[quoted text clipped - 3 lines]
> left side (earliest opened) start to close by themselves as newer files are
> opened. [...]

I haven't seen that those are the files
from the left only. These usually are
the ones I work on, too, while the ones
on the right are those I hit furing
debugging and I often wouldn't even
miss them. So I think with me it's
seemingly random ones.
But I might be wrong and will look for
this.

Schobi

Signature

SpamTrap@gmx.de is never read
I'm Schobi at suespammers dot org

"The presence of those seeking the truth is infinitely
to be prefered to those thinking they've found it."
Terry Pratchett

Reply to this Message

Hendrik Schober - 11 Nov 2004 16:10 GMT

> > [...]
> >
[quoted text clipped - 8 lines]
> But I might be wrong and will look for
> this.

OK, I just had this again. I had about
six or eight files open, and ended up
with three. The leftmost one still is
open (although I think I moved it to
the leftmost position manually). And it
did not save the file I had just started
to edit when I stopped the app I was
debugging (using SHIFT-F5, BTW).

Schobi

Signature

SpamTrap@gmx.de is never read
I'm Schobi at suespammers dot org

"The presence of those seeking the truth is infinitely
to be prefered to those thinking they've found it."
Terry Pratchett

Reply to this Message

Tarek Madkour [MSFT] - 11 Nov 2004 20:39 GMT

> OK, I just had this again. I had about
> six or eight files open, and ended up
[quoted text clipped - 4 lines]
> to edit when I stopped the app I was
> debugging (using SHIFT-F5, BTW).

The debugger QA team is taking another look at this bug trying to
reproduce it in our labs.

Thanks,

Signature

Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.

Reply to this Message

Peter Bromley - 10 Nov 2004 21:31 GMT

I have found that this can happen both on beginning and ending debug
sessions. The IDE may close a subset of files or all files - it seems
completely random. If a file is unsaved and closed by the IDE, it DOES
NOT get saved. Grrrr.

As I debug immediately after a build, the fact it closes files is an
annoyance only as there are generally no unsaved files. But when
debugging, I sometimes change files as I detect small fixes or change
comments, and then I can get bitten bad!

Others in my workplace have found this problem to be bad enough to
preclude the use of Edit and Continue, so we do not use this anymore.

Sorry I can't offer anything more concrete than anecdotal evidence of a
problem, but I can say it seems to be unrelated to the number of files open.

Peter

>>>I have about 20 source files open when I start a debug session. Then
>>>all of them are closed! Why is that?? Very annonying. Project is C++,
[quoted text clipped - 15 lines]
>
> Thanks,

Signature

If you wish to reply to me directly, my addres is spam proofed as:

pbromley at adi dot co dot nz

Or if you prefer - nospam@nowhere.com :-)

Reply to this Message

Tarek Madkour [MSFT] - 10 Nov 2004 22:38 GMT

> I have found that this can happen both on beginning and ending
> debug sessions. The IDE may close a subset of files or all files
> - it seems completely random. If a file is unsaved and closed by
> the IDE, it DOES NOT get saved. Grrrr.

I'll have the QA team try again to reproduce this. It seems that
quite a number of you are hitting it... and it is a data loss which
makes it even more critical.

Thanks,

Signature

Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.

Reply to this Message

Sean Cavanaugh - 10 Nov 2004 23:55 GMT

Edit-and-Continue for me definitely makes the IDE crash for me multiple
times in one day, but only one some days (full moons and eclipses?).
And the only thing extra I have installed is the fast-build-solution
plugin (but everyone runs that, right? :).

> I have found that this can happen both on beginning and ending debug
> sessions. The IDE may close a subset of files or all files - it seems
[quoted text clipped - 34 lines]
>>
>> Thanks,

Reply to this Message

Hendrik Schober - 11 Nov 2004 11:30 GMT

> Edit-and-Continue for me definitely makes the IDE crash for me multiple
> times in one day, but only one some days (full moons and eclipses?).
> And the only thing extra I have installed is the fast-build-solution
> plugin (but everyone runs that, right? :).

I have it and Visual Assist, too.
However, I think the problem had bitten me
before I had those.

> [...]

Schobi

Signature

SpamTrap@gmx.de is never read
I'm Schobi at suespammers dot org

"The presence of those seeking the truth is infinitely
to be prefered to those thinking they've found it."
Terry Pratchett

Reply to this Message

Hendrik Schober - 11 Nov 2004 18:41 GMT

> I have found that this can happen both on beginning and ending debug
> sessions. [...]

Seems this isn't my day. I just had the
IDE close files unwanted the second time
today. Surprisingly this time it was the
very first time I noticed that when I was
/starting/ the debugger.

Schobi

P.S.: Oh, and I think it closed the file
which I had opened last...

Signature

SpamTrap@gmx.de is never read
I'm Schobi at suespammers dot org

"The presence of those seeking the truth is infinitely
to be prefered to those thinking they've found it."
Terry Pratchett

Reply to this Message

7.1 IDE bug

Free Magazines