This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
signed/unsigned char
- From: Milena Constantino Caires <milena at registro dot br>
- To: gcc-help at gcc dot gnu dot org
- Date: Wed, 20 Jul 2005 11:45:55 -0300
- Subject: signed/unsigned char
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