signed/unsigned char

Milena Constantino Caires milena@registro.br
Wed Jul 20 14:46:00 GMT 2005


I would like to know why the following statements do not generate a
error during compiling but they do generate segmentation fault and
core dump when the program is running:


char* c = new char(1024);

or

u_char* c = new u_char(1024);

I know that the correct form of this memory allocation is "[1024]" and not
"(1024)" but sometimes it occurs by mistake.

The compiler is not supposed to complain about it???

Thanks in advance,
Milena



More information about the Gcc-help mailing list