Yea that could be (I had a feeling it was pointer but was not 100% sure)
But the problem is WHERE .. alot of changes to the HL2MP sdk so it could be
anywhere
I find it very rare that 2 people would hit the exact same address
violations with an error in our code.
Unless it is code that is the exact same on both machines, which would be a
sdk file ..
Does that sound about right?
r00t 3:16
CQC Gaming
www.cqc-gaming.com
----- Original Message -----
From: "Jeffrey "botman" Broome" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, June 03, 2005 1:49 PM
Subject: Re: [hlcoders] Application error with update.
Stephen Micheals wrote:
i just finished merging the new code into my mod and it compiled
perfectly and then on load i get a assert in the file mempool.cpp
@line 177
Assertion Failed: pBlob
if i ignore the assert right after it will crash out with the same
The instruction at "0x01286080" referenced memory at "0x01286080" The
memory could not be "read"
as yours.
If the instruction at 0x01286080 is trying to read memory at 0x01286080
(the same as the instruction address) then you have a messed up pointer
somewhere (some pointer is being assigned the address of code and then
trying to dereference the pointer).
Perhaps you are not passing parameters to a function properly and the
return address for some code is being assigned to some pointer?
--
Jeffrey "botman" Broome
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
