I haven't coded or ran a mud in about 5 years now and I've forgotten the command to debug my game. I went to look at mudbytes for any hints but I about died from the eyebleed that the site has turned in to.

I remember there was a command that when the game crashed it would stop, and I could step in to the next line of code and see what was causing the issue. The directions may have been on Nick Gammon's website. I'll go look over there as well.

I remember using valgrind for memory leaks and would like to have a decent command for that again. I think I had a copy/paste of the valgrind that I was using at the time, but must have lost it along the way.

Any help is appreciated.

that would be running it in gdb instead of using the startup script and this is the one i have for valgrind

valgrind -v --tool=memcheck --leak-check=yes --show-reachable=yes --db-attach=yes --num-callers=10 --track-fds=yes --suppressions=src/specials/vg_suppress.supp ./LOP 2700

of course change the stuff as you need thats just what I used lol