Char arrays filled with 0xCC after allocation

Question

-52 = 0xCC

So after allocating char array in debugging windows I can see my array is filled with 0xCC. What does it mean? (-52 = 0xCC)

You will find the answer here: http://stackoverflow.com/questions/370195/when-and-why-will-an-os-initialise-memory-to-0xcd-0xdd-etc-on-malloc-free-new — AdamF, Apr 27 '15 at 19:31

score 2 · Accepted Answer · answered Apr 27 '15 at 19:31

Uninitialized built-in types have an in-determined value, trying to read it is undefined behavior.

The actual values you can see depend on the compiler: You might for example see garbage, zeroes or (what seems to be the case in your example) some special value indicating "data uninitialized".

RichieHindle · Answer 2 · 2015-04-27T19:36:29.547

1

It's there as a sentinel value so that you know that the memory is uninitialized.

See the /GZ compiler switch.

edited Apr 27 '15 at 19:36

answered Apr 27 '15 at 19:30

RichieHindle

258,929
46
350
392

Char arrays filled with 0xCC after allocation

2 Answers2