You are wrongly using an hack to pass an integer to a thread. The idea behind what you are doing is an integer is 4 bytes and a pointer is 4 bytes in x86_32 (8 bytes in x86_64) so I can convert an integer type to a pointer type and then convert it back to … Read more
It also happens if you’re trying to access an instance when you have a pointer, and vice versa: As pointed out in a comment, this can be made excruciating if someone goes and typedefs a pointer, i.e. includes the * in a typedef, like so: Because then you get code that looks like it’s dealing with instances, when in fact … Read more
You can’t directly do array2 = array1, because in this case you manipulate the addresses of the arrays (char *) and not of their inner values (char). What you, conceptually, want is to do is iterate through all the chars of your source (array1) and copy them to the destination (array2). There are several ways to … Read more
Pointer arithmetic is always in terms of the size of the pointed-to object(s). Incrementing a char* will advance the address by one, whereas for int* it would usually be four (bytes). But void has unknown size, so pointer arithmetic on void* is not allowed by the standard. Cast to the appropriate type first; if you just want to manipulate the address as if … Read more
This looks wrong: Should probably be: (spaces added for convenience). EDIT: Some additional explanation: When you say return_data[i]=… you are trying to write something into return_data[i]. Now, return_data is char**, so return_data[i] is char*. So you are writing a pointer into some location in memory. It looks like your pointers are 8 bytes long (which is fine), but you’ve only allocated 6 bytes: MAX_SOURCE_STRING+1. So … Read more
In read_response, you are probably overwriting the end of the buffer pointed to by buf. The problem is that buf is a pointer, so sizeof(buf) will return the size of a pointer (probably 4 or 8 depending on your CPU). You are using sizeof as if buf were an array, which is not really the same thing as a pointer in C although … Read more
How you detect EOF depends on what you’re using to read the stream: Check the result of the input call for the appropriate condition above, then call feof() to determine if the result was due to hitting EOF or some other error. Using fgets(): Using fscanf(): Using fgetc(): Using fread(): Note that the form is the same for all of them: … Read more
Your fprintf call has 8 format specifiers but passes 9 further arguments to fill these. The 8th format specifier is %d; the argument corresponding to this is Item[i]->Name. The warning is telling you that Item[i]->Name is a string so can’t (shouldn’t) be converted to a signed integer. I presume Item[i]->Price has type int; you then either need to add an extra %s to your format string … Read more
A line loop is just an outline. To fill the middle as well, you want to use GL_POLYGON.