Related:

• 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....
• core: n. Main storage or RAM. Dates from the days of ferrite-core memory
  ow archaic as techspeak most places outside IBM, but also still used in the UNIX community and by old-time hackers or those who would sound like them....
• core n. Main storage or RAM. Dates from the days of ferrite-core memory
  ow archaic as techspeak most places outside IBM, but also still used in the Unix community and by old-time hackers or those who would sound like them....
• brain dump n. [common] The act of telling someone everything one knows about a particular topic or project.
  Typically used when someone is going to let a new party maintain a piece of code....
• brain dump: n. The act of telling someone everything one knows about a particular topic or project.
  Typically used when someone is going to let a new party maintain a piece of code....
• pam vt.,vi.,n. [from "Monty Python's Flying Circus"] 1.
  To crash a program by overrunning a fixed-size buffer with excessively large input data....
• examining the entrails: n. The process of {grovel}ling 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....
• 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....
• 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....