Well, if you were idle when you crashed then perhaps something in the game's normal processes took it down, maybe look through comm.c's heartbeat and check some things. Could it possibly do with the mud having a problem writing to a file, or a missing file, so forth? Offtopic though, isn't there a better form of examining program crashs for Windows? I only rely on gdb in *nix, something akin to that would make it a lot simpler for people to find out whats happening. -- +---------------------------------------------------------------+ | FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html | | Archives: http://post.queensu.ca/listserv/wwwarch/circle.html | +---------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/06/01 PST