[Qt-interest] help tracking down memory corruption on Mac Qt 4.7.3 Cocoa (64 bit)

[Paul Miller]

On 5/25/2011 7:46 AM, Paul Miller wrote:
>>> Konrad - that would be worth looking into except I am building with
>>> XCode. This is the first thing I thought of, because I've
>>> seen this kind
>>> of thing before (a *LONG* time ago, when using make), but not since
>>> using Visual Studio and XCode for my builds. When I change
>>> the header, I
>>> always see the "compiling X/Y files" message and the number
>>> is correct -
>>> it's rebuilding all of the files that depend on the header.
>>
>> Hi Paul,
>>
>> Even though you say all of the dependencies are being built, I know QMake
>> for XCode is buggy - in both 4.7.2 and 4.6.0, I regularly have to rebuild
>> twice after changing a UI file.  The first build seems to run uic, but not
>> recompile the form code itself.  Next build does the form code.
>
> I'm not using QMake. I build my projects directly in XCode.
>
> All evidence points to a compiler bug.

Okay I'm back, and my moving variables around didn't solve the problem.

But, I DID find the problem.

I'm using GLEW, and it defines GLuint as an unsigned long as Apple 
defines it (in the OpenGL framework) as an unsigned int.

So when I created a texture using glGenTextures(), it was probably 
trying to treat an int (32 bits) as a long (64 bits), or vice versa.

Something to be aware of!