Re: x86 process memory map

2020-03-31 Thread Konstantin Belousov
On Tue, Mar 31, 2020 at 03:04:18PM +0200, Paul FLOYD wrote: > > It is the stack grow area and the guard, combined. Read the mmap(2), in> > > particular explanation of MAP_STACK and MAP_GUARD. > I see from the mmap man page that this appeared in FreeBSD 11.1. >   > Do you know where the size of

Re: x86 process memory map

2020-03-31 Thread Paul FLOYD
> It is the stack grow area and the guard, combined. Read the mmap(2), in> > particular explanation of MAP_STACK and MAP_GUARD. I see from the mmap man page that this appeared in FreeBSD 11.1.   Do you know where the size of the stack guard gets defined? I tried searching on google for stuff

Re: x86 process memory map

2020-03-30 Thread Paul FLOYD
> It is the stack grow area and the guard, combined. Read the mmap(2), in > particular explanation of MAP_STACK and MAP_GUARD. OK, thanks very much. I will go and read the man page. A+ Paul ___ freebsd-toolchain@freebsd.org mailing list

Re: x86 process memory map

2020-03-30 Thread Konstantin Belousov
On Mon, Mar 30, 2020 at 08:18:08AM +0200, Paul Floyd wrote: > When I run procstat on a small 32bit app that just calls sleep (on FreeBSD > 12.1 amd64) then I see at the end of the map > > 22353 0xfbffe000 0xfffde000 ---00 0 0 - -- > 22353 0xfffde000

x86 process memory map

2020-03-30 Thread Paul Floyd
When I run procstat on a small 32bit app that just calls sleep (on FreeBSD 12.1 amd64) then I see at the end of the map 22353 0xfbffe000 0xfffde000 ---00 0 0 - -- 22353 0xfffde000 0xe000 rw-33 1 0 ---D- df 22353 0xe000