You wrote: > On Sat, 9 Dec 1995 SROWAN@WVNVAXA.WVNET.EDU wrote: > > > Ok, here's something interesting i just ran across.. Our circle > > mud sometimes crashes for no apparent reason... when i go and > > check the core, it gives me a file and line, etc. Well i go look > > at the code, and see nothing wrong with it, so i reboot and try > > the same command, and guess what, it works without crashing. No > > matter what i do, i can't recreate the conditions of the crash.. > > for example it crashes when an immort types go <wrong mob name>, > > but when the mud reboots and we try it again, it works... > > > > I know this sounds far fetched, but we run off a pentium 60 at > > the moment, could this be caused by a faulty intel chip? or do > > you have another solution? This seems to be pointer trouble, quite common in C. Any pointer in your program is writing out of bounds, probably messing up data used by another function, so the command will only crash if the buggy command was executed first and has messed up the memory for the second one. Those are the hardest bugs to find in a program and there is no general hint. Take a close look at the commands implemented lately and check ALL pointers if they write out of bounds. Good luck. Cat.
This archive was generated by hypermail 2b30 : 12/07/00 PST