Buffer Overrun Warnings (Windows Embedded CE 6.0)
1/5/2010
The Code Analysis tool detects some situations in which buffer overruns occur, including array bounds violations.
For more information about Code Analysis warnings, see this Microsoft Web site.
The following warnings are reported in this category:
| Warning | Description |
|---|---|
C6029 |
Possible buffer overrun in call to <function>. |
C6057 |
Buffer overrun due to number of characters/number of bytes mismatch in call to <function>. |
C6201 |
Buffer overrun for <variable>, which is possibly stack allocated: index <name> is out of valid index range <min> to <max> |
C6202 |
Buffer overrun for <variable>, which is possibly stack allocated, in call to <function>: length <size> exceeds buffer size <max> |
C6203 |
Buffer overrun for buffer <variable> in call to <function>: length <size> exceeds buffer size |
C6204 |
Possible buffer overrun in call to <function>: use of unchecked parameter <variable> |
C6209 |
Using 'sizeof<variable1>' as parameter <number> in call to <function> where <variable2> may be an array of wide characters, did you intend to use character count rather than byte count? |
C6292 |
Ill-defined for-loop: counts up from maximum |
C6293 |
Ill-defined for-loop: counts down from minimum |
C6294 |
Ill-defined for-loop: initial condition does not satisfy test. Loop body not executed |
C6295 |
Ill-defined for-loop: <variable> values are of the range "min" to "max". Loop executed indefinitely |
C6296 |
Ill-defined for-loop: Loop body only executed once |