BUG: An "MSDEV.EXE - Application Error" error message occurs when you try to build using the command-line features of Msdev.exe (235680)
The information in this article applies to:
- Microsoft Visual C++, 32-bit Enterprise Edition 6.0
- Microsoft Visual C++, 32-bit Professional Edition 6.0
- Microsoft Visual C++, 32-bit Learning Edition 6.0
This article was previously published under Q235680 SYMPTOMS While performing a build using the command-line features of
Msdev.exe, the following error appears: DDE Server Window
: MSDEV.EXE - Application Error : The instruction at "0x50084b23" referenced
memory at "0x00000014". The memory could not be "read". If
Visual C++ is the default debugger, clicking Cancel from the error message will
launch Visual C++ to debug the crash. It will then display a message stating
that the crash took place in Devshl.dll. CAUSE The WM_SYSCOLORCHANGE Windows message was sent to a hidden
Developer Studio window during the build. Developer Studio does not properly
handle the WM_SYSCOLORCHANGE message when building from the
command-line.
This problem can happen when using Symantec's
PCAnywhere to build a project on a remote computer. When you quit PCAnywhere,
the remote computer will receive the WM_SYSCOLORCHANGE message. Other
applications that generate a WM_SYSCOLORCHANGE message would have the same
problem. RESOLUTION Avoid changing the system's display settings while an
Msdev.exe command-line build is in progress. This may be difficult if the
source of the WM_SYSCOLORCHANGE message is unknown or if this message is
unavoidable. Consider exporting make files (.mak) for the project
and building the project using the NMake utility. To export a make file, select
Export Make File from the Project menu in Developer Studio. You can also have make files exported
automatically whenever the project changes by doing the following:
- On the Tools menu, click Options.
- On the Build tab, select the Export makefile when saving project file check box.
This guarantees that the make file is always synchronized with
the project file.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in Microsoft Visual C++
.NET.
Modification Type: | Major | Last Reviewed: | 9/2/2005 |
---|
Keywords: | kbtshoot kbBug kbDevStudio kbide kbNoUpdate KB235680 kbAudDeveloper |
---|
|