You can find most bugs by looking at the core dump
with GDB. From my source directory I use the following
command to look at the core dump:
gdb ../bin/circle ../lib/core
once in GDB, type back and it will list the last five
functions calls before the crash. You can also use
'print' to display variable values at the time of the
crash.
WC
-----Original Message-----
From: Quinn ShadowStalker <quinn@MUD.COMSYS.NET>
To: CIRCLE@post.queensu.ca <CIRCLE@post.queensu.ca>
Date: Thursday, May 14, 1998 12:59 PM
Subject: GDB Question
>how would I start GDB to check for bugs in my bin/circle? Cause my mud
>seems to crash for unknown reasons alot.
>
>-------------------------------------------------------------------------|
>|Matt Roach - owner of OnyxMUD | "I dont have bugs... |
>|matt@shiva.ml.org quinn@mud.comsys.net| randomly created freatures!" |
>-------------------------------------------------------------------------|
>
>
> +------------------------------------------------------------+
> | Ensure that you have read the CircleMUD Mailing List FAQ: |
> | http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
> +------------------------------------------------------------+
+------------------------------------------------------------+
| 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