Quote:Original post by ehmdjii
yes it seems that the problem is elsewhere, cause it looks like the instance that is accessed later on when the problem occurs, is a complete different one.
but how can this happen? how can an instance be created without passing through the constructor?
Quote:Original post by ehmdjii
button b0, b1, b2, b3, b4, b5, b6, b7;
button buttonArray[8] = {b0, b1, b2, b3, b4, b5, b6, b7};
Quote:Original post by ehmdjiiIn VC2005 (It'll be similar for other Visual Studio versions), put a breakpoint just after where you construct the variable, then when it's hit go to Debug -> New Breakpoint -> New Data Breakpoint, put in "&mouseover" for the address, and hit OK.
thank you,
excuse the stupid question, but what is a "data"-breakpoint? :-)
Quote:Original post by ehmdjiiIt sounds like you're reading too many bytes and overflowing whatever buffer you're writing into.
it's not. :) sorry
ok, i found out what a data breakpoint is, used it and it turns out that the data is modified in another class's constructor during an fread.
Quote:Original post by Evil Steve
It sounds like you're reading too many bytes and overflowing whatever buffer you're writing into.
size_t bytestoread = width * height * depth; size_t bytesread = 0; pixels = (GLubyte * )malloc(bytestoread); bytesread = fread(pixels, 1, bytestoread, filepointer); if(bytesread != bytestoread) { err = "Byte read mismatch"; }
