Related:

• chase pointers 1. vi. To go through multiple levels of indirection, as in traversing a linked list or graph structure.
  Used esp. by programmers in C, where explicit pointers are a very common data type....
• vaxocentrism /vak`soh-sen'trizm/ n. [analogy with `ethnocentrism'] A notional disease said to afflict C programmers who persist in coding according to certain assumptions that are valid (esp.
  under Unix) on VAXen but false elsewhere. Among these are...
• wizzle: v. To convert external names, array indice
  or references within a data structure into address pointers when the data structure is brought into main memory from external storage (also called `pointer swizzling')...
• core dump: n. [common {Iron Age} jargon, preserved by UNIX] 1.
  [techspeak] A copy of the contents of {core}, produced when a process is aborted by certain kinds of internal error....
• egmentation fault n. [Unix] 1. [techspeak] An error in which a running program attempts to access memory not allocated to it and core dumps with a segmentation violation error.
  This is often caused by improper usage of pointers in the source code, dereferencing a null pointer, or (in C) inadvertently using a non-pointer variable as a pointer....
• ap: v. To replace a pointer to a pointer with a direct pointe
  to replace an old address with the forwarding address found there....
• chain: 1. [orig. from BASIC's `CHAIN' statement] vi.
  To hand off execution to a child or successor without going through the {OS} command interpreter that invoked it....
• aliasing bug: n. A class of subtle programming errors that can arise in code that does dynamic allocation, esp.
  via `malloc(3)' or equivalent. If several pointers address (`aliases for') a given hunk of storage, it may happen that the storage is freed or reallocated (and thus moved) through one alias and then referenced through another, which may lead to subtle (and possibly intermittent) lossage depending on the state and the allocation history of the malloc {arena}....
• chain 1. vi. [orig. from BASIC's CHAIN statement] To hand off execution to a child or successor without going through the OS command interpreter that invoked it.
  The state of the parent program is lost and there is no returning to it....