Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualNightCreature83

Posted 01 August 2013 - 03:05 AM

What happens is that the value inside the vector becomes 30000ish from its original value. The passed in vector is not newed it is stack allocated and passed as a const reference to both functions. This means that when the code comes to figuring out which texture coordinate definition to choose it messes up.

After all your posts and seeing that it is to acces trying certain things through the tinyXml mempool in the asm, gives me a starting point.

@Pink Horror: the memory that is written to is on the stack not the heap and isnt explicitly being freed nor is that vector being cleared in between these calls.

The offending asm line is:
Mov qword pointer [rax], rcx
At the end of the new block.

#2NightCreature83

Posted 01 August 2013 - 03:02 AM

What happens is that the value inside the vector becomes 30000ish from its original value. The passed in vector is not newed it is stack allocated and passed as a const reference to both functions. This means that when the code comes to figuring out which texture coordinate definition to choose it messes up.

After all your posts and seeing that it is to acces trying certain things through the tinyXml mempool in the asm, gives me a starting point.

@Pink Horror: the memory that is written to is on the stack not the heap and isnt explicitly being freed nor is that vector being cleared in between these calls.

#1NightCreature83

Posted 01 August 2013 - 02:59 AM

What happens is that the value inside the vector becomes 30000ish from its original value. The passed in vector is not newed it is stack allocated and passed as a const reference to both functions. This means that when the code comes to figuring out which texture coordinate definition to choose it messes up.

After all your posts and seeing that it is to acces trying certain things through the tinyXml mempool in the asm, gives me a starting point.

PARTNERS