Re: gdb [CIRCLE] [CODE]

From: Mysidia (
Date: 07/01/00

On Sat, 1 Jul 2000, Felix J Vazquez wrote:

> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-redhat-linux".
> Core was generated by `bin/circle -q 5001'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x808e61e in ?? ()
> (gdb)

   It basically means it can't find a name in the symbol table for the
address of the function it thinks it's in -- a number of things can cause
that to happen, most-common ones being...

  (1) The program file that generated the corefile has been changed or
      is different than the one currently on disk

  (2) The program was either compiled with -O / -O2 / -O3 /... or
      was not compiled with the -g flag

  (3) The contents of the stack frame/pointer in memory got scrambled,
      by something such as a buffer overflow or writing to an invalid
      pointer -- did you try using the 'bt' gdb command to check if
      the whole backtrace is 'in ??' ?.

  (4) Gdb doesn't like you today, try finding a way to reproduce the bug
      and use breakpointing to identify the fault or try getting and
      analyzing another corefile. <chuckle


     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     |  |

This archive was generated by hypermail 2b30 : 04/10/01 PDT