Physical Mayhem Bug wrote:
Also, no matter what the stack looks like, it always ends up in the same code
path, which is something like:
mov edx,dword ptr [edi+20h]
Do you know how to read assembler? In case you don't, here's a primer:
This is assigning to a dereferenced pointer. It's something like:
pSomething->m_iID = i;
edi holds a pointer to an object (pSomething), 20h is the offset to
whatever data is wanted (m_iID is 0x20 bytes into pSomething's data
structure), and finally it will move whatever is in edx into that memory
address. It may look like gibberish to a layman, but it and the
contextual code actually mean something.
What's important though is not what it says exactly, because that's
pretty tough to figure out without alot of work, but rather what
addressed the program crashed at. I see one crash here, just the top of
the stack:
vphysics.dll!260a2426()
vphysics.dll!260d3eae()
vphysics.dll!2608af8e()
here's another:
vphysics.dll!260a1f40()
vphysics.dll!260b6240()
vphysics.dll!2609444b()
and a third:
vphysics.dll!2609993d()
tier0.dll!008738de()
vphysics.dll!26009ce9()
that's three different places. If those stack traces are indeed
accurate, then I count three individual crashes. Even if the three
places all have that same hex instruction, they probably do different
things and are separate crashes.
--
Jorge "Vino" Rodriguez
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
