Re: top_of_zone_table?

From: Daniel A. Koepke (dkoepke@circlemud.org)
Date: 10/06/02


On Sun, 6 Oct 2002, Templar Viper wrote:

> I traced the bug, finally after loads of hours.

It should be as easy as:

  % gdb bin/circle
  (gdb) watch top_of_zone_table
  Hardware watchpoint 1: top_of_zone_table
  (gdb) run -q 4001


> And for some reason i cannot see, it changes the value of top_of_zone_table,
> with corruption as result.

More than liekly GM_TRAINER(index) is not returning a valid index into
mob_index[].  C's arrays are not bounds-checked (for efficiency), and so
if you overrun them, you write into other memory.


> Now what is so weird about this, is that on cygwin everything worked
> normal, even with the faulthy code, but on redhat.. bugs all the way.

That's not terribly unusual.  Windows is seemingly very good at hiding
rather serious bugs.

-dak

--
   +---------------------------------------------------------------+
   | FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
   | Archives: http://post.queensu.ca/listserv/wwwarch/circle.html |
   | Newbie List:  http://groups.yahoo.com/group/circle-newbies/   |
   +---------------------------------------------------------------+



This archive was generated by hypermail 2b30 : 06/25/03 PDT