Hello, Were you the one who issued the mstat command? If someone creates a mob using OLC or adds a mobprog that isn't coded correctly, Issuing the mstat command will cause the mud to crash.
>>Lastly, does anyone know of a way to find memory leaks? Are you running on linux? If you, you should download GNU Lint and also read the docs.. Lint will give you a ton of more infomation about your mud over GDB. Lint will also tell you if sytax is wrong or various other possibile warnings in your code that GDB won't or may not catch. I rarely hear mention of this I guess since most people rely on what is most popular or well known.. But read up on lint.. I personally think it's great. Links to great tools for Mud Developers.. The first 3 tools are for Linux, The last one, API Monitor is for Windows.. A good program for those using windows/mysql and Rom. Valgrind: The distribution currently includes five tools: two memory error detectors, a thread error detector, a cache profiler and a heap profiler. http://valgrind.org/ Slint: Splint is a tool for statically checking C programs for security vulnerabilities and coding mistakes. http://www.splint.org/ Data Display Debugger: DDD is a graphical front-end for command-line debuggers such as GDB, DBX, WDB, Ladebug, JDB, XDB, the Perl debugger, the bash debugger, or the Python debugger. DDD displays data structures as graphs and plots. http://sourceforge.net/projects/ddd/ API Monitor for Windows Users: API Monitor is a software that monitors and displays API calls made by applications. Its a powerful tool for seeing how Windows and other applications work or tracking down problems that you have in your own applications. http://www.rohitab.com/apimonitor/ Hope this helps, Chris
