> > and that's where it crashed. > > > > the core dump is long gone, becuase i was just looking thru the > > syslog.(1<->6) in the ..log dir. > > any suggestions? > > The core won't tell you much. I just experimented with a self-induced > infinite loop and was able to get the command that caused the loop, but > nothing more detailed. That may steer you in the right direction. If you > can catch it in the act (unusually long lag), you can attach gdb to it and > ctrl-C will show you exactly where you're stuck. > If you need a quick break out of a program, and need a core dump, use the abort() function. Technically speaking, an infinte loop isn't a code problem per se, its a performace problem, so gdb could care less about it. You could setp lots of break points though, but an infine loop ought to be immediately apparent. PjD +------------------------------------------------------------+ | Ensure that you have read the CircleMUD Mailing List FAQ: | | http://democracy.queensu.ca/~fletcher/Circle/list-faq.html | +------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST