On 01.06.2012, at 02:44, Peter Maydell wrote: > On 30 May 2012 13:45, Alexander Graf <ag...@suse.de> wrote: >> When reading our faked /proc/self/maps from a secondary thread, >> we get an invalid stack entry. This is because ts->stack_base is not >> initialized in non-primary threads. >> >> However, ts->info is, and the stack layout information we're looking >> for is there too. So let's use that one instead! > > So in the multithreaded case do all the thread stacks live > in this one mapping, or do the non-primary thread stacks > live in a standard mmap'd mapping?
I thought /proc/self/maps always shows the initial stack map as [stack]? Alex
