我在阅读C/C++的记忆布局时也处于同样的两难境地。 在这方面,我随后把这些问题清除起来。

http://www.geeksforgeeks.org/memory-layout-of-c-program/。

此处添加了主要示例:

我希望这有助于找到类似问题的答案。

(说明:下文适用于六氯环己烷)

这一过程的 st脚和ap积存在于记忆过程的“ame”部分。 差距和差距在相互之间发展(最初,当进程启动时,梯子占据了整个地区,可以由 st和肥皂组合而占据;每个记忆分配(小型/免费/新的/支离式)可以推动 st与 he之间的边界。 黑海经合组织科也位于同一个由本组织分配的工地上,它有自己的部分,包含全球变量。 只读的数据在数据栏中,包括插图字等内容。 例如,如果你的法典有以下几条内容:

char tmpStr[] = "hello";

之后,包含“hello”的源代码部分将居住在数据部分。

一本关于此内容的良好、彻底的书籍是E.Briant计算机系统。

作为答复的增编,本文引自。 GotW ,将一些主要记忆领域分类(指的是自由建筑之间的区别,这是我通常称为肥皂,而实际肥皂则是通过小型/免费管理的一部分)。 该条是过时的,因此我不知道它是否适用于现代C++;到目前为止,我没有发现直接矛盾。

Const Data The const data area stores string literals and other data whose values are known at compile time. No objects of class type can exist in this area. All data in this area is available during the entire lifetime of the program. Further, all of this data is read-only, and the results of trying to modify it are undefined. This is in part because even the underlying storage format is subject to arbitrary optimization by the implementation. For example, a particular compiler may store string literals in overlapping objects if it wants to.

Stack The stack stores automatic variables. Typically allocation is much faster than for dynamic storage (heap or free store) because a memory allocation involves only pointer increment rather than more complex management. Objects are constructed immediately after memory is allocated and destroyed immediately before memory is deallocated, so there is no opportunity for programmers to directly manipulate allocated but uninitialized stack space (barring willful tampering using explicit dtors and placement new).

Free Store The free store is one of the two dynamic memory areas, allocated/freed by new/delete. Object lifetime can be less than the time the storage is allocated; that is, free store objects can have memory allocated without being immediately initialized, and can be destroyed without the memory being immediately deallocated. During the period when the storage is allocated but outside the object s lifetime, the storage may be accessed and manipulated through a void* but none of the proto-object s nonstatic members or member functions may be accessed, have their addresses taken, or be otherwise manipulated.

Heap The heap is the other dynamic memory area, allocated/freed by malloc/free and their variants. Note that while the default global new and delete might be implemented in terms of malloc and free by a particular compiler, the heap is not the same as free store and memory allocated in one area cannot be safely deallocated in the other. Memory allocated from the heap can be used for objects of class type by placement-new construction and explicit destruction. If so used, the notes about free store object lifetime apply similarly here.

Global/Static Global or static variables and objects have their storage allocated at program startup, but may not be initialized until after the program has begun executing. For instance, a static variable in a function is initialized only the first time program execution passes through its definition. The order of initialization of global variables across translation units is not defined, and special care is needed to manage dependencies between global objects (including class statics). As always, uninitialized proto- objects storage may be accessed and manipulated through a void* but no nonstatic members or member functions may be used or referenced outside the object s actual lifetime.