On Sun, 2006-09-10 at 20:14 +0700, Mulyadi Santosa wrote: > Hi Arjan... > > > what happens is when you use threads, glibc makes additional stacks > > in addition to the original one that the kernel made for the process, > > and the threads start using those. Those stacks aren't marked "stack" > > in /proc/<pid>/maps and friends, because the kernel doesn't really > > know that they are stacks. And that is perfectly fine; a "stack" is > > not something special that the kernel needs to care about. Well not > > after having set one up that is. > > Hm, thanks for the additional info, Arjan. I really appreciate it. > > BTW, is this "stack" a TLS sement? Is it defined in Program Header > Table? it's not a tls segment, it's just a piece of (non-executable) memory that is mmaped. Again there is nothing magical about being stack or not... it's just memory. -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
