On 28-04-08 16:58, Rene Herman wrote:
Anyways, usually, even when not guaranteed anything, you'd expect to be
able to in practice get the same address. I know recent Red Hat
distributions use addressspace randomization which easily could
interfere. I suppose you are using Debian:
`- Debian
On Tue, Apr 29, 2008 at 12:29 AM, 李一 [EMAIL PROTECTED] wrote:
thx!
On Mon, Apr 28, 2008 at 10:58 PM, Rene Herman [EMAIL PROTECTED]
wrote:
On 28-04-08 12:44, ?? wrote:
I got a problem here: I have a large share memory (say, 1.5GB) to be
mapped into several processes' address space, I
thx!
On Mon, Apr 28, 2008 at 10:58 PM, Rene Herman [EMAIL PROTECTED]
wrote:
On 28-04-08 12:44, ?? wrote:
I got a problem here: I have a large share memory (say, 1.5GB) to be
mapped into several processes' address space, I wanna make sure that the
addresses those processes use to map the
Why would heap randomization prevent me from getting a same address?
On Mon, Apr 28, 2008 at 11:14 PM, Rene Herman [EMAIL PROTECTED]
wrote:
On 28-04-08 16:58, Rene Herman wrote:
Anyways, usually, even when not guaranteed anything, you'd expect to be
able to in practice get the same address.
On 28-04-08 18:36, ?? wrote:
Why would heap randomization prevent me from getting a same address?
Because in process B the heap could be placed in the region where your 1,5G
map is in process A, meaning shmat needs to map elsewhere.
Rene
--
To unsubscribe from this list: send an email
On 28-04-08 18:40, Rene Herman wrote:
On 28-04-08 18:36, ?? wrote:
Why would heap randomization prevent me from getting a same address?
Because in process B the heap could be placed in the region where your
1,5G map is in process A, meaning shmat needs to map elsewhere.
Looking closer,
Rene Herman wrote:
Looking closer, the CONFIG option keeps non-heap address-space
randomization enabled. What you want to have is:
$ cat /proc/sys/kernel/randomize_va_space
0
Set it, as root, via
# echo -n 0 /proc/sys/kernel/randomize_va_space
Off topic, but do you need the -n flag? I
Rene Herman wrote:
On 28-04-08 19:31, Scott Lovenberg wrote:
Rene Herman wrote:
Looking closer, the CONFIG option keeps non-heap address-space
randomization enabled. What you want to have is:
$ cat /proc/sys/kernel/randomize_va_space
0
Set it, as root, via
# echo -n 0
