imported>Kvng: MOS:TERM

2025-11-28T16:09:58Z

← Previous revision		Revision as of 16:09, 28 November 2025
Line 1:		Line 1:
			{{Short description\|Software programming error}}

	A '''stale pointer bug''', otherwise known as an '''aliasing bug''', is a class of subtle programming errors that can arise in code that does [[dynamic memory allocation]], especially via the [[malloc]] function or equivalent.		A '''stale pointer bug''', otherwise known as an '''aliasing bug''', is a class of subtle programming errors that can arise in code that does [[dynamic memory allocation]], especially via the [[malloc]] function or equivalent.

	If several [[pointer (computer programming)\|pointer]]s address (are "[[pointer aliasing\|aliases]] for") a given chunk 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) errors depending on the state and the allocation history of the malloc arena. This bug can be avoided by never creating aliases for allocated memory,<ref name="FOLDOC">{{foldoc\|stale+pointer+bug}}</ref> by controlling the dynamic [[scope (programming)\|scope]] of references to the storage so that none can remain when it is freed, or by use of a [[garbage collection (computer science)\|garbage collector]], in the form of an intelligent memory-allocation library or as provided by [[high-level programming language\|higher-level languages]], such as [[Lisp programming language\|Lisp]].		If several [[pointer (computer programming)\|pointer]]s address (are [[pointer aliasing\|aliases]] for) a given chunk 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) errors depending on the state and the allocation history of the malloc arena. This bug can be avoided by never creating aliases for allocated memory,<ref name="FOLDOC">{{foldoc\|stale+pointer+bug}}</ref> by controlling the dynamic [[scope (programming)\|scope]] of references to the storage so that none can remain when it is freed, or by use of a [[garbage collection (computer science)\|garbage collector]], in the form of an intelligent memory-allocation library or as provided by [[high-level programming language\|higher-level languages]], such as [[Lisp programming language\|Lisp]].

	The term "aliasing bug" is nowadays associated with [[C (programming language)\|C]] programming, but it was already in use in a very similar sense in the [[ALGOL]] 60 and [[Fortran]] programming language communities in the 1960s.<ref name="FOLDOC" />		The term ''aliasing bug'' is nowadays associated with [[C (programming language)\|C]] programming, but it was already in use in a very similar sense in the [[ALGOL]] 60 and [[Fortran]] programming language communities in the 1960s.<ref name="FOLDOC" />

	==See also==		==See also==
Line 13:		Line 15:
	[[Category:Software bugs]]		[[Category:Software bugs]]
	[[Category:Software_anomalies]]		[[Category:Software_anomalies]]


	{{software-eng-stub}}		{{software-eng-stub}}

imported>Kvng: foldoc attribution, see Template_talk:FOLDOC#It_doesn't_matter_whether_readers_care

2024-11-21T21:54:48Z

foldoc attribution, see Template_talk:FOLDOC#It_doesn't_matter_whether_readers_care

New page

A '''stale pointer bug''', otherwise known as an '''aliasing bug''', is a class of subtle programming errors that can arise in code that does [[dynamic memory allocation]], especially via the [[malloc]] function or equivalent.

If several [[pointer (computer programming)|pointer]]s address (are "[[pointer aliasing|aliases]] for") a given chunk 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) errors depending on the state and the allocation history of the malloc arena. This bug can be avoided by never creating aliases for allocated memory,<ref name="FOLDOC">{{foldoc|stale+pointer+bug}}</ref> by controlling the dynamic [[scope (programming)|scope]] of references to the storage so that none can remain when it is freed, or by use of a [[garbage collection (computer science)|garbage collector]], in the form of an intelligent memory-allocation library or as provided by [[high-level programming language|higher-level languages]], such as [[Lisp programming language|Lisp]].

The term "aliasing bug" is nowadays associated with [[C (programming language)|C]] programming, but it was already in use in a very similar sense in the [[ALGOL]] 60 and [[Fortran]] programming language communities in the 1960s.<ref name="FOLDOC" />

==See also==
*[[Dangling pointer]]

==References==
{{Reflist}}

[[Category:Software bugs]]
[[Category:Software_anomalies]]

{{software-eng-stub}}

Stale pointer bug - Revision history

imported>Kvng: MOS:TERM

imported>Kvng: foldoc attribution, see Template_talk:FOLDOC#It_doesn't_matter_whether_readers_care