|
From: Tom H. <th...@cy...> - 2004-10-10 17:30:19
|
In message <Pin...@jd...>
Igmar Palsenberg <mai...@jd...> wrote:
>
> > > The limit actually get's set, but is never raised. This triggers grsec,
> > > which rightfully complains that later allocations in the data segment
> > > exceed the existing limits.
> >
> > When you that it is never raised, what do you mean? It isn't supposed
> > to be raised in the valgrinded process - that is the whole point. It
> > should be restored on exec however. Is that what you are saying isn't
> > happening?
>
> I was confused by the manual page of brk(), since that indicates brk()
> returning -1 is things fail. Looking at the kernel code, brk() failing
> just returns the current data segment border.
I believe there are substantial differences between what the brk
system call does and what the brk() function in glibc does, so you
might want to look at glibc as well.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|