Q45183: Incorrect Handling of SP Can Cause CodeView to Corrupt Stack
Article: Q45183 Product(s): See article Version(s): 2.20 2.30 | 2.20 2.30 Operating System(s): MS-DOS | OS/2 Keyword(s): ENDUSER | | mspl13_basic Last Modified: 7-JUN-1989 CodeView will use your program's stack for temporary variables in between assembly instructions. Thus, when writing an assembly language program, if you forget to increase the stack pointer (SP) to point beyond the memory locations you are using on the stack, CodeView will overwrite that memory. This is expected behavior. Even if CodeView did not use the stack, you would still have to increment the stack pointer to keep your program from overwriting your variables when you make a call, or with any operation that pushes values on the stack.
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
Copyright Microsoft Corporation 1986-2002.