Backov
05-25-2007, 01:02 PM
I believe my nice new, couple month old uber-machine has just failed on me.
I'm happily coding along, and all of a sudden I get a failure deep inside the VC code, on this line:
std::stringstream ss;
I get a fail (randomly) in this, and later down I get a fail (deep inside Ogres code) when it trys to new 496 bytes! Since when does new fail? The return is a no memory exception.
So, considering I've got hundreds of gigs of free HD space, 2 gigs of ram, and a brand new machine - what's going on here?
Is it possible I've managed to mess up new with out of bounds writes? Does that allocation code live in the same memory space as my program? Or is this for sure a hardware problem?
I'm happily coding along, and all of a sudden I get a failure deep inside the VC code, on this line:
std::stringstream ss;
I get a fail (randomly) in this, and later down I get a fail (deep inside Ogres code) when it trys to new 496 bytes! Since when does new fail? The return is a no memory exception.
So, considering I've got hundreds of gigs of free HD space, 2 gigs of ram, and a brand new machine - what's going on here?
Is it possible I've managed to mess up new with out of bounds writes? Does that allocation code live in the same memory space as my program? Or is this for sure a hardware problem?