My best suggestion is to go to the line that it said it crashed on (which
you didn't list in your message) and start printing the values of everything
on that line. You can't use MACROS, so you'll have to type all the direct
pointers into the structs manually. Usually this way it gives you a better
idea on what happened. Normally in a case like this, it is a problem
somewhere else in the code and you will have a hell of a time finding it.
ltrace seems to be the way to go when you do find which value was "Cannot
access memory at address ..." and follow that around until it goes wild.
Some common prints:
print ch->player.name
print obj->name
Of course I could be way off here...
Rick
-----Original Message-----
From: Julian Buckley <s348266@student.uq.edu.au>
To: CIRCLE@post.queensu.ca <CIRCLE@post.queensu.ca>
Date: Thursday, March 04, 1999 6:36 PM
Subject: [GDB] Understanding Output
>Heya list...
>
>Forgive me if this seems an elementary question, but I'm just trying to
>work out gdb output's and the like...
>
>The mud crashed today whilst in sedit, and I got this from gdb:
>(gdb) bt
>#0 shop_keeper (ch=0x3e7460, me=0x380ce8, cmd=310, argument=0xffc64
>"sedit") at shop.c:844
>Cannot access memory at address 0xef7ff744.
>
>What's the simple definition of it, and is it fixable?
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST