> 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.
I've found the best way to kill and infinite loop to send the mud a
kill -11 [mud-pid]. There are lots of other signals you can send to
the mud to produce a core, but my code is used to signal 11 the most,
so I don't want to upset it with SIGABRT.
---
Matt Knecht <hex@voicenet.com> - The official Minister of Redundancy Minister
of the next millenium!
+------------------------------------------------------------+
| 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