Well, learn how to use gdb well :) Commands like back (backtrace) will show you what was happening in your mud up till the crash, list to list code around the crash site. You can use print to check out the variables (print n, etc, you can use casts when printing to make more sense of it). Look for a full gdb tutorial somewhere, then if you haven't figured out your problem by then, paste us the gdb code along with backtrace, list, and so forth.. -- +---------------------------------------------------------------+ | 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