Stack overflow
In software, a stack overflow occurs if the call stack pointer exceeds the stack bound. The call stack may consist of a limited amount of address space, often determined at the start of the program. The size of the call stack depends on many factors, including the programming language, machine architecture, multi-threading, and amount of available memory. When a program attempts to use more space than is available on the call stack (that is, when it attempts to access memory beyond the call stack's bounds, which is essentially a buffer overflow), the stack is said to overflow, typically resulting in a program crash.
- Comment
- enIn software, a stack overflow occurs if the call stack pointer exceeds the stack bound. The call stack may consist of a limited amount of address space, often determined at the start of the program. The size of the call stack depends on many factors, including the programming language, machine architecture, multi-threading, and amount of available memory. When a program attempts to use more space than is available on the call stack (that is, when it attempts to access memory beyond the call stack's bounds, which is essentially a buffer overflow), the stack is said to overflow, typically resulting in a program crash.
- Date
- 4 November 2022
- Has abstract
- enIn software, a stack overflow occurs if the call stack pointer exceeds the stack bound. The call stack may consist of a limited amount of address space, often determined at the start of the program. The size of the call stack depends on many factors, including the programming language, machine architecture, multi-threading, and amount of available memory. When a program attempts to use more space than is available on the call stack (that is, when it attempts to access memory beyond the call stack's bounds, which is essentially a buffer overflow), the stack is said to overflow, typically resulting in a program crash.
- Is primary topic of
- Stack overflow
- Label
- enStack overflow
- Link from a Wikipage to an external page
- software.intel.com/en-us/blogs/2010/07/01/the-reasons-why-64-bit-programs-require-more-stack-memory/
- web.archive.org/web/20171104123645/http:/software.intel.com/en-us/blogs/2010/07/01/the-reasons-why-64-bit-programs-require-more-stack-memory/
- Link from a Wikipage to another Wikipage
- Address space
- Buffer overflow
- C (programming language)
- C++
- Call stack
- Category:Computer errors
- Category:Software bugs
- C dynamic memory allocation
- Crash (computing)
- Double fault
- Double-precision floating-point format
- GNU Compiler Collection
- Heap overflow
- Kernel (computer science)
- Megabytes
- Primitive recursive function
- Scheme (programming language)
- Segmentation fault
- Stack (abstract data type)
- Stack buffer overflow
- Tail-call optimization
- Tail recursion
- SameAs
- Dépassement de pile
- LfTt
- Lỗi tràn ngăn xếp
- m.051fqk
- Pinon ylivuotovirhe
- Přetečení zásobníku
- Przepełnienie stosu
- Q13218767
- Stack overflow
- Stack overflow
- Stack overflow
- Stack overflow
- Переповнення стека
- Переполнение стека
- גלישת מחסנית
- سرریز پشته
- スタックオーバーフロー
- 堆疊溢位
- 스택 오버플로
- Subject
- Category:Computer errors
- Category:Software bugs
- Url
- https://web.archive.org/web/20171104123645/http:/software.intel.com/en-us/blogs/2010/07/01/the-reasons-why-64-bit-programs-require-more-stack-memory/
- WasDerivedFrom
- Stack overflow?oldid=1118792029&ns=0
- WikiPageLength
- 9662
- Wikipage page ID
- 1436888
- Wikipage revision ID
- 1118792029
- WikiPageUsesTemplate
- Template:For multi
- Template:Main
- Template:Memory management navbox
- Template:Reflist
- Template:Short description
- Template:Webarchive