The nice thing about backtrace is that it does just THAT, it traces your problem generally rather well. It steps back through where the signal was trapped and says what happened and where the core was generated. > #2 0x00456760 in do_function (ch=0xd01574, do_fun=0x46dae0 <do_skills>, did you make any changes to do_skills????? Even the smallest addition could set it off, if you don't know what you're doing. > > Error: Cannot access memory at address 0xd0a2a24 > IIRC, this is GENERALLY generated by a core dump when the following things have happened (not all are required, just a few examples): A> You've allocated memory, then free'd it before calling the result, calling it AFTER it's been freed (woops).
B> You've overrun your memory boundaries (char buf [MSL]; is not ALWAYS big enough to handle everything, though usually it is). How do I fix the problem??? RUN the mud in gdb (see the mailing list F.A.Q for how).. Step it where you know the problem is (again RTFM). 10:1, this is a memory allocaton problem, and can be solved EASILY by knowing what you're doing! -- TJW :Head tech, designer, bum:P Mud :http://dreamless.wolfstream.net telnet :telnet://dreamless.wolfstream.net 9275 OLC Pages:http://olc.wolfstream.net
