Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 474
  • Last Modified:

MS Visual C++ 6.0 (SP 5) CRASHES!

Sometimes the MSDEV studio application crashes during compiling and I'm not talking about the compiler, but the MSDEV.exe application.  The crashes are always different (ie--different instruction address/memory address), but the same thing always occurs:

It pauses for like 2 seconds and then blamo, studio dies.  Has anyone seen this symptom?  It only happens under win2000, nt4 never had this problem.  This problem occurs on both of my win2000 boxes.

Let me know if anyone has seen this, I have searched the mircrosoft site and cannot find anything.  The latest SP5 has been applied numerous times.
0
toddmoore
Asked:
toddmoore
  • 5
  • 3
  • 2
  • +4
1 Solution
 
nietodCommented:
Are there old versions of the MS development tools on the computer?   i.e. might it be finding a version 5 ccompiler/linker

Try creating a make file for the project and run the make file in "steps" to see what step it is crashing in.

Does the problem occur with all source code, or just a particular file?
0
 
jdrescherCommented:
Are you running any addins on visual studio? I've had many developer studio crashes using them, however most of the time the crashes were either gui related or during shutdown / startup of msdev. I have not seen msdev crash like you say and I do all my development / testing on 5 different win2k boxes, with sp5 and win2k sp2. Have you tried deleting the .ncb, .aps, .clw and other developer studio generated files. These files sometimes become corrupt and cause msdev problems.
0
 
snoeglerCommented:
Is your computer stable otherwise? Bad RAM can cause this problems; MSDEV takes up lots of space.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
IainHereCommented:
You could try turning all macros off - I recently added a macro for automatically increasing the version number with each build and it crashed all builds I attempted except on the original project.  Like nietod asked - does it always do it, or just with certain projects / files?
0
 
jdrescherCommented:
I do now recall that I had the same kind of crashes while writing a buildcount addin. I remember it was related to the COM interface to msdev, but I don't remember any specifics.
0
 
toddmooreAuthor Commented:
I use Rational Purify and Quantify, but they were both disengaged when compiling.  My computer at home does the same thing, and those components are not installed.

I did upgrade my work computer from NT 4 to Win2000.  That actually might be when I first started to notice the occasional crash.  

My workaround is to save all changed files before compiling.  It will not crash if I do that.  However, If I just compile and it auto-saves before compile, that is when it sometimes crashes...
0
 
nietodCommented:
Does this do this with a newly created project?  i.e. create  simple basic project from scratch and test this.
0
 
IainHereCommented:
>> However, If I just compile and it auto-saves before compile, that is when it sometimes crashes...

I've noticed that on my machine - it was happening when I tightened the access rights of a member function or variable.  Even though nothing was trying to access the offending item, the compiler still crashed.  I think it also happened sometimes when I changed functions to be virtual.  Is this what you're doing when you see the problem.  I'm afraid I didn't do anything clever to solve the problem - just saved the files before compiling.
0
 
toddmooreAuthor Commented:
I could not recreate using a new small project.  The project I was compiling during blowup consists of about 10 projects in the workspace, everything is source safe enabled, and many of the projects are dependents of other projects.  Nothing too complicated and pretty standard with a commercial product.

0
 
nietodCommented:
There you have it.  Keep your projects to 1 file under 100 lines and you will be fine.  any other questions?

I would start making the small project mroe like the large one or vice versa and see where the problem occurs/dissapears.  I realsize that is a pain, but its probably your best bet.  there is hope, you know that its not a permentant problem.  You know it can be turned on or off soemhow.  So now you need to see what turns it on or off.  Then--hopefully--its something you can afford to turn off.
0
 
toddmooreAuthor Commented:
haha...  I'll try to keep our future software under 100 lines of code.  Sure would reduce the bug count too. ;)

Don't really have much time to investigate this further.  Using the work around of saving before compiling will do for now.  Surprised many other folks have not experienced this, so it I guess it could be within our project files... oh well, had to ask.  thanks everyone.
0
 
griesshCommented:
I think you forgot this question. I will ask Community Support to close it unless you finalize it within 7 days. Unless there is objection or further activity,  I will suggest to refund the points and PAQ for 0 points since nobody had an answer for you.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
======
Werner

0
 
toddmooreAuthor Commented:
that's fine.  i still have the problem.
0
 
snoeglerCommented:
In the meantime i have also experienced the same problem using VC 6.0 SP3+.

In our team the problem you describe seems to happen more often if you are editing code and then without delay press F7 to build the project. I'd guess it could be that Intellisense has some background threads running which are analysing what you're typing while suddenly the build command interrupts them. I also noticed that MSDEV hangs 1-2 seconds before the crash happens. If you do not move the mouse or hit any key in this time (i.e. do not issue a message to the IDE frame window), most of the time no crash happens. I did not notice that behavior in the new IDE.
0
 
toddmooreAuthor Commented:
Seems like you are experiencing exactly what I'm seeing.  I installed 6.0 SP 5 and still had problems.  The new IDE (.net) has not crashed (yet).

I can also recreate the problem by clicking on the FILE-SAVE toolbar button as fast as I can.  It will usually say something about not being able to access the file.  I have even seen it blow away the file that I was saving when I do this.  Not good!

I imagine this problem will not be fixed as the new IDE is MS's main focus.
0
 
MindphaserCommented:
Force accepted

** Mindphaser - Community Support Moderator **
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 5
  • 3
  • 2
  • +4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now