Mercurial > hg > early-roguelike
view urogue/TODO @ 288:b8919055c2fc
UltraRogue: compile out the built-in memory checking.
Functions in memory.c tracked and instrumented memory allocation. This
mechanism logged information to a text file and also added a 16KB guard
area to every allocation. Neither of these are desirable in a multi-
user environment, so the whole memory tracking subsystem has been
disabled.
The behavior can be enabled with a configure flag, but it would be a
better idea to use Valgrind to deal with memory bugs.
| author | John "Elwin" Edwards |
|---|---|
| date | Fri, 24 Nov 2017 13:22:26 -0500 |
| parents | c495a4f288c6 |
| children |
line wrap: on
line source
UltraRogue: The Ultimate Adventure in the Dungeons of Doom Copyright (C) 1993, 1995 Herb Chong All rights reserved. %W% %G% add_pack() calls ur_free() on the linked list pointer passed to it. Need to go through code and look for cases where we use that pointer after calling add_pack(). Electric fence in guard-free() mode should help. Similary throw_away(), discard(), discard_pack() free items... there will be more like this... Bug in genocide scroll: don't request list, type letter, etc... Implement potion of true sight. Bug: apparently when creating a new familiar after a player level change, something isn't begin reset because ur SEGVs when running through the monster list in do_chase() right after the new familiar is created. It appears that the familiar isn't being removed from the monster list.