堆栈上的内存分配和缓冲区溢出，x86ISA32-AllocationofmemoryonthestackandBufferOverflow,x86ISA32

2  

The x86 architecture was heavily influenced by Intel 8080, which had a similar stack architecture (one shared call and data stack growing downward). At the time this was seen as a significant advance, given that the 8080's predecessor, the 8008, had a call stack that was built into the CPU and that was only seven levels deep.

x86架构受到英特尔8080的严重影响，英特尔8080具有类似的堆栈架构（一个共享呼叫和数据堆栈向下增长）。当时这被认为是一个重大的进步，因为8080的前身8008有一个内置在CPU中的调用堆栈，只有七个级别。

Intel 8080 was released in 1974. Given that not a lot of stuff was networked (for example, Ethernet was just being developed), potential stack smashing attacks were probably not a major concern. Flexibility, and making good use the of the available RAM, on the other hand, were.

英特尔8080于1974年发布。鉴于没有很多东西被联网（例如，以太网刚刚开发），潜在的堆栈粉碎攻击可能不是主要问题。另一方面，灵活性，并充分利用可用的RAM。

It was much later that stack smashing became a major concern. For example, the first high-quality step-by-step guide was published in 1996.

很久以后，堆栈粉碎成为一个主要问题。例如，第一份高质量的逐步指南于1996年出版。

1  

Historically, stack and heap occupied the same memory space. Heap was allocated from the bottom, while stack from the top. When you overflow... you would just overwrite the other space memory and soon lead to a crash.

从历史上看，堆栈和堆占用了相同的内存空间。堆从底部分配，而堆栈从顶部分配。当你溢出......你只会覆盖其他空间内存并很快导致崩溃。

Nowdays, I believe, it is no longer the case, but the x86 instruction set for managing stack remained so that it consumes memory from top.

我相信，现在已经不再是这样，但是用于管理堆栈的x86指令集依然存在，以至于它从顶层消耗内存。

But arrays are indexed from the bottom. For that reason array[0] is closer to the "top" of the stack (which is below), and array[n-1] is further away.

但阵列是从底部索引的。因此，array [0]更接近堆栈的“顶部”（在下面），而array [n-1]更远。