I was just curious what the best way to debug a crash from circle is?
Normally you'd look where you got a warning in the compile process, but
sometimes it compiles cleanly.
Everytime I do a gdb --core=circle.core it just tells me it was started by
"circle -q 4000" and it failed from a segmentation fault. Am I missing a
switch that will give me more info?
Is there other options of gdb or some other debugger to help track down
where in the code it's crashing?
- Brian
+------------------------------------------------------------+
| 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