Which mod, clientside or serverside? give a link to the debug file? ati or nivdia?
Valve is usually very helpful in these matters, as long as you can give them a place to fix.. nick to whatever it takes to find a way to replicate the crash. On Sat, Oct 2, 2010 at 6:54 AM, Andrew Watkins <[email protected]> wrote: > Our mod regularly produces a server crash in engine.dll. A memory dump is > produced, but this contains only a single frame, which is *always* > 0bad04d0(). There is no assembler code listed. > > This crash has lurked in the background for some time, but is happening with > greater regularity in the latest version of the mod. We cannot reliably > reproduce the crash, indeed we don't know what causes it when it does > happen. I have a vague inling that it may be triggered by players connecting > / disconnecting, but that's little more than a hunch. We have only ever had > this crash on our beta test server once, but it's cropping up on public > servers quite regularly. > > I'm at a loss for how to proceed with this. Without being able to trigger > the crash reliably, rolling back to previous versions and checking if it > still occurs it isn't viable. What we really need is a way of determining > the trigger, but for that, we need to be able to cause the error. > > Given that it's in engine.dll, and it just produces a single frame, I > imagine there's some sort of memory corruption going on. I've looked through > everything I can think of in our code, but have come up with nothing. Does > anybody have any experience with debugging crashes like this, or any > suggestions on a useful tool to use - bearing in mind that we don't have the > source code for the dll that is supposedly causing the error? > > Thanks in advance! > _______________________________________________ > 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

