Skip to Main Content
Idaho State University

Glossary

Filter:
# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z All
A
A1
AC
ACD
ACK
ACL
ACU
A-D
Ada
ADC
ADH
ADM
ADP
AE
AES
AFJ
AFR
AI
AIG
AIN
AIS
AJ
AK
AKM
ALC
ALE
ALU
AMA
AMI
AMS
ANI
AOS
AP
APC
APD
APL
App
APU
AR
Arg
ARQ
ARS
ASU
AV
AVP
Aliasing Bug
  • 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. Avoidable by use of allocation strategies that never alias allocated core, or by use of higher-level languages, such as LISP, which employ a garbage collector (see GC). Also called a stale pointer bug. See also precedence lossage, smash the stack, fandango on core, memory leak, memory smash, spam. Historical noteThough this term is nowadays associated with C programming, it was already in use in a very similar sense in the Algol-60 and FORTRAN communities in the 1960s.