Besides global memory, threads also share a number of other attributes (i.e., these attributes are global to a process, rather than specific to a thread). These attributes include the following: process ID and parent process ID; process group ID and session ID; controlling terminal; process credentials (user and group IDs); open file descriptors; record locks created using fcntl(); signal dispositions; file system–related information: umask, current working directory, and root directory; interval timers (setitimer()) and POSIX timers (timer_create()); System V semaphore undo (semadj) values (Section 47.8); resource limits; CPU time consumed (as returned by times()); resources consumed (as returned by getrusage()); and nice value (set by setpriority() and nice()). Among the attributes that are distinct for each thread are the following: thread ID (Section 29.5); signal mask; thread-specific data (Section 31.3); alternate signal stack (sigaltstack()); the errno variable; floating-point environment (see fenv(3)); realtime scheduling policy and priority (Sections 35.2 and 35.3); CPU affinity (Linux-specific, described in Section 35.4); capabilities (Linux-specific, described in Chapter 39); and stack (local variables and function call linkage information).

摘自:《Linux编程接口:Linux和UNIX系统编程手册》，Michael Kerrisk，第619页

告诉面试官这完全取决于操作系统的实现。

以Windows x86为例。只有两个段[1]，代码和数据。它们都被映射到整个2GB(线性，用户)地址空间。基础= 0,限制= 2 gb。他们本来可以做一个，但x86不允许一个段同时读/写和执行。所以他们做了两个，并设置CS指向代码描述符，其余(DS, ES, SS等)指向另一个[2]。但两者都指向同样的东西!

面试你的人做了一个隐藏的假设，他/她没有说出来，这是一个愚蠢的伎俩。

所以关于

问:告诉我是哪个线段 分享吗?

细分市场与问题无关，至少在Windows上是这样。线程共享整个地址空间。只有一个堆栈段SS，它指向DS ES CS做的完全一样的东西[2]。比如整个用户空间。0-2GB。当然，这并不意味着线程只有一个堆栈。当然，每个都有自己的堆栈，但x86段并不用于此目的。

也许*nix做一些不同的事情。谁知道呢。这个问题的前提被打破了。

至少对于用户空间是这样的。 从ntsd记事本:cs=001b ss=0023 ds=0023 es=0023

来自维基百科(我认为这对面试官来说是个很好的回答:P)

Threads differ from traditional multitasking operating system processes in that: processes are typically independent, while threads exist as subsets of a process processes carry considerable state information, whereas multiple threads within a process share state as well as memory and other resources processes have separate address spaces, whereas threads share their address space processes interact only through system-provided inter-process communication mechanisms. Context switching between threads in the same process is typically faster than context switching between processes.

线程共享堆(有一个关于线程特定堆的研究)，但当前的实现共享堆。(当然还有代码)

线程共享所有内容[1]。整个进程只有一个地址空间。

每个线程都有自己的堆栈和寄存器，但所有线程的堆栈都在共享地址空间中可见。

如果一个线程在它的堆栈上分配了某个对象，并将该地址发送给另一个线程，它们对该对象的访问权是相等的。

实际上，我刚刚注意到一个更广泛的问题:我认为你混淆了segment这个词的两种用法。

可执行文件(如ELF)的文件格式有不同的部分，可以称为段，包含编译的代码(文本)、初始化的数据、链接器符号、调试信息等。这里没有堆段或堆栈段，因为它们是仅运行时结构。

这些二进制文件段可以分别映射到进程地址空间，具有不同的权限(例如，对于代码/文本，只读可执行;对于初始化的数据，写时复制不可执行)。

根据约定(由语言运行库强制执行)，这个地址空间的区域用于不同的目的，如堆分配和线程堆栈。不过，这些都只是内存，并且可能没有分段，除非您在虚拟8086模式下运行。每个线程的堆栈是在线程创建时分配的内存块，当前堆栈顶部地址存储在堆栈指针寄存器中，每个线程保留自己的堆栈指针和其他寄存器。

好的，我知道:信号掩码，TSS/TSD等。地址空间，包括它所有映射的程序段，仍然是共享的。

Besides global memory, threads also share a number of other attributes (i.e., these attributes are global to a process, rather than specific to a thread). These attributes include the following: process ID and parent process ID; process group ID and session ID; controlling terminal; process credentials (user and group IDs); open file descriptors; record locks created using fcntl(); signal dispositions; file system–related information: umask, current working directory, and root directory; interval timers (setitimer()) and POSIX timers (timer_create()); System V semaphore undo (semadj) values (Section 47.8); resource limits; CPU time consumed (as returned by times()); resources consumed (as returned by getrusage()); and nice value (set by setpriority() and nice()). Among the attributes that are distinct for each thread are the following: thread ID (Section 29.5); signal mask; thread-specific data (Section 31.3); alternate signal stack (sigaltstack()); the errno variable; floating-point environment (see fenv(3)); realtime scheduling policy and priority (Sections 35.2 and 35.3); CPU affinity (Linux-specific, described in Section 35.4); capabilities (Linux-specific, described in Chapter 39); and stack (local variables and function call linkage information).

摘自:《Linux编程接口:Linux和UNIX系统编程手册》，Michael Kerrisk，第619页