no error in compiling time, no error while running, but I just feel insecure. I tested the size of returned space, it was 4. don't know why not 0?????
what wrong with it?
Code:char *space = NULL; size = GetSize(text); /* zero returned to "size" */ space = malloc(size); lstrcpy(space, "\0"); /* initialize "space" */
I'm guessing you're testing the size of the returned space by doing something like:
This is returning the size of the pointer which points to the allocated memory. The reason it is returning 4 is that pointers on 32 bit machines are 4 bytes. If malloc() succeeds, then the size of the buffer that is returned is always equal to the size in bytes of the value passed to malloc().Code:int sizeofspace = sizeof(space)
>space = malloc(size);
If size is zero, then you may find that space is actually a NULL pointer (or maybe not). In any event, you can't dereference the pointer since no bytes have been allocated.
The only valid thing you could do at this point would be
free( space );
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
It's hard to explain without the context in the code. I will paste them here.
Here I need to make sure one thing first. How to initial a variable as follows:
Code:LPSTR textOutput = NULL; textOutput = malloc(1024); lstrcpy(textOutput, "\0"); /* Initialization, is it correct? */
Don't know what lstrcpy is. I'd use
KurtCode:if ( 0 != textOutput ) { /* malloc successful */ textOutput[0]='\0'; /* initialize to "" */ ..... else { /* malloc did not return a valid pointer */ }
lstrcpy is almost the same as strcpy. (Maybe, not very sure.)
And question here is, malloc(0) also returns a valid pointer but not NULL, so I am worrying when textOutput[0] = '\0', it is exactly writing on a place where doesn't belong to it.
If you're not sure what it does, you really shouldn't be using it.lstrcpy is almost the same as strcpy. (Maybe, not very sure.)
Your best bet is to avoid passing 0 to malloc() in the first place. It's an easy case to test for, or you can write your code to keep it from ever giving you 0 for a non-error condition.And question here is, malloc(0) also returns a valid pointer but not NULL, so I am worrying when textOutput[0] = '\0', it is exactly writing on a place where doesn't belong to it.
Just because I don't care doesn't mean I don't understand.
I just referred to msdn help and knew that lstrspy also deals with wide charactor, unicode.
