Compiler gives warnings I don't understand

[Gerread]

My current problem is about the compiler giving warnings that don't make sense to me, as in I don't understand why they're happening.

"initialization makes pointer from integer without a cast"

The variable in question is an unsigned char*. It is initialised by a function which returns an unsigned char*. I honsetly can't find the problem there. I'm returning a pointer, not an integer. I made casted the return value as (unsigned char*) so I could shut it up, but now that I'm getting unexplained segmentation faults out of nowhere I think it's time to find out why it's happening...I have multiple functions which are doing this.

EDIT: Just realised I posted in the windows forum :/...Could someone please move it to windows forum since there's no delete?

[robwhit]

what is the code?

[Gerread]

Declared:

unsigned char* mem = function();

Proto:

unsigned char* function(void);

Relevant function part:

//memory to be returned
	unsigned char* retmem = malloc(size);

...

	//return memory
	return retmem;

[Salem]

It's probably complaining about the malloc call.
Did you include stdlib.h ?

Because without it, malloc is implicitly declared as returning an int.
Hence the "makes pointer from integer" part of the message.

[Gerread]

That stopped it from complaining. Thanks for the insight. I suppose that means wtih including stdlib, I can just cast it as whatever. It didn't fix the crashing (ofcourse) but it's one less thing to suspect. I guess I'll have to rewrite and pray I don't do whatever I did to screw it up.

[Salem]

> I can just cast it as whatever.
NO!
casting malloc would merely mean that you no longer get the warning at all. It's not the same as fixing the real problem (not including the header file).

Also, are you using C or C++ (don't be vague and say C/C++).
If it's C++, then you really should be using new/delete and not malloc/free.

[Gerread]

I am using C here. I'll take your advice and remove the casts in favour of stdlib.