I read in my unix text book that bss is used to store the uninitialized variables(global declarations). This would mean that the static variables are stored separately and n
The original idea is still there, although there are layers of obfuscation on top of it for local symbols, small references, shared libraries, and such.
But everything is still based on the original simple model and so it is worth knowing. The idea is that there are three segments.
Bss is special: .bss objects don't take any space in the object file, and by grouping all the symbols that are not specifically intialized together, they can be easily zeroed out at once.
Static has a couple of meanings. In one sense it is just a symbol attribute that tells the linker whether it is local to an object module or can be globally linked with other symbols of the same name. It is also used to specify storage duration, to distinguish objects within a function from automatic (stack allocated) objects.
So a static variable can be in either data or bss depending on whether it is initialized or not, as can a global.
bss
is traditionally the so-called uninitialized variables, but C and Unix guarantee they are initialized to zero. (See this.) It is a portion of the data segment, usually right after the program-statically-initialized-variable space. Just higher in memory than bss is usually the beginning of the heap.