Related:

• examining the entrails n. The process of grovelling through a core dump or hex image in an attempt to discover the bug that brought a program or system down.
  The reference is to divination from the entrails of a sacrified animal....
• casting the runes: n. What a {guru} does when you ask him or her to run a particular program and type at it because it never works for anyone else
  esp. used when nobody can ever see what the guru is doing different from what J....
• dump: n. 1. An undigested and voluminous mass of information about a problem or the state of a system
  especially one routed to the slowest available output device (compare {core dump}), and most especially one consisting of hex or octal {runes} describing the byte-by-byte state of memory, mass storage, or some file....
• dump n. 1. An undigested and voluminous mass of information about a problem or the state of a system
  especially one routed to the slowest available output device (compare core dump), and most especially one consisting of hex or octal runes describing the byte-by-byte state of memory, mass storage, or some file....
• 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....
• hyperspace: /hi:'per-spays/ n. A memory location that is *far* away from where the program counter should be pointing, often inaccessible because it is not even mapped in.
  Another core dump --- looks like the program jumped off to hyperspace somehow....
• wango: /wang'goh/ n. Random bit-level {grovel}ling going on in a system during some unspecified operation.
  Often used in combination with {mumble}. For example...
• unes: pl.n. 1. Anything that requires {heavy wizardry} or {black art} to {parse}
  core dumps, JCL commands, APL, or code in a language you haven't a clue how to read....
• desk check: n.,v. To {grovel} over hardcopy of source code, mentally simulating the control flow
  a method of catching bugs. No longer common practice in this age of on-screen editing, fast compiles, and sophisticated debuggers --- though some maintain stoutly that it ought to be....