Yeah, if the callstack does not include any of the .dll's then it's a system-level (or lower) crash. Your code can cause it though, and it's not easy detecting exactly what caused it. The easiest way to debug such mysterious errors is to debug them the moment they begin to crash, and not keep implemting new features with new bugs, it just makes it hard to find out what's causing the first bugs.
If you cannot fix the bugs by debugging, you migth need to strip your features out one by one by reverting to the valve-stock-code. It's a nightmare, but it's not that bad, I've done it several times. And an army of testers are the best thing in the world! ----- Original Message ----- From: "Jorge Rodriguez" <[email protected]> To: <[email protected]>; "Discussion of Half-Life Programming" <[email protected]> Sent: Friday, August 07, 2009 5:00 PM Subject: Re: [hlcoders] Awkward crash dumps > On Fri, Aug 7, 2009 at 5:58 AM, <[email protected]> wrote: > >> * A crash where the call stack ONLY shows a memory address? Not even any >> mention of a dll. This is our most common crash, and happens 1-2 times a >> day >> on each server. >> > > > These are usually crashes dealing with the user's hardware. Video card > drivers or operating system failures of some kind. Sometimes something > that > you do in the mod's programming can screw up the engine and make it crash > though, good luck finding that. > > As for a Linux client, I would find that rather surprising if you had one. > > -- > Jorge "Vino" Rodriguez > _______________________________________________ > 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
