diff -r 4891d49809bb -r 2b3996fc09a1 core/com.nokia.carbide.cpp.compiler.doc.user/html/pragmas_x86/p_fill_stack.htm --- a/core/com.nokia.carbide.cpp.compiler.doc.user/html/pragmas_x86/p_fill_stack.htm Mon Jul 19 15:31:48 2010 -0500 +++ b/core/com.nokia.carbide.cpp.compiler.doc.user/html/pragmas_x86/p_fill_stack.htm Mon Jul 19 16:13:24 2010 -0500 @@ -1,24 +1,24 @@ - - - - - -fill_stack - - - -

fill_stack

-

Instructs the compiler to initialize locals to a fixed bit pattern (0xCC) upon entry to a function.

-
Syntax
-

#pragma fill_stack on | off | reset

-
Targets
- Intel x86
-
Remarks
-

Use of this pragma helps to diagnose program failures or crashes caused by the use of uninitialized variables. I.e., a bit pattern of 0xCC is not a normally-encountered integer or floating-point value, and 0xCCCCCCCC is almost never a valide pointer value. If the program counter does point to such a variable, it will be “executed” as an int3 breakpoint.

-

This pragma does not correspond to any panel setting. To check this setting, use the __option (fill_stack). The default setting for is off at optimization level 0.
-

- - - - - + + + + + +fill_stack + + + +

fill_stack

+

Instructs the compiler to initialize locals to a fixed bit pattern (0xCC) upon entry to a function.

+
Syntax
+

#pragma fill_stack on | off | reset

+
Targets
+ Intel x86
+
Remarks
+

Use of this pragma helps to diagnose program failures or crashes caused by the use of uninitialized variables. I.e., a bit pattern of 0xCC is not a normally-encountered integer or floating-point value, and 0xCCCCCCCC is almost never a valide pointer value. If the program counter does point to such a variable, it will be “executed” as an int3 breakpoint.

+

This pragma does not correspond to any panel setting. To check this setting, use the __option (fill_stack). The default setting for is off at optimization level 0.
+

+ + + + +