Hi!
> > Abel, I actually don't think you have chance to have any issues with
> > randomization, as the mentioned post talks about 2.6.22.10, which doesn't
> > randomize the brk start at all.
>
> You are rigth, my kernel just randomizes stack top.
>
> I've got a bit sick with this crash in the la
2008/2/4, Jiri Kosina <[EMAIL PROTECTED]>:
> Abel, I actually don't think you have chance to have any issues with
> randomization, as the mentioned post talks about 2.6.22.10, which doesn't
> randomize the brk start at all.
You are rigth, my kernel just randomizes stack top.
I've got a bit sick
On Mon, 4 Feb 2008, Abel Bernabeu wrote:
> > > I think I am getting the some problem with brand new binaries produced
> > > by myself :(
> > > Look at this report I posted days ago:
> > > http://marc.info/?l=linux-kernel&m=120169141603789&w=2
> > Your crash is in kernel, no? Anyway, I can workarou
2008/2/4, Pavel Machek <[EMAIL PROTECTED]>:
> > >
> > > > I still don't seem to fully understand what is happening here --
> > > > aparently this is triggerable only with old programs linked against
> > > > libc.so.5, and I am not able to trigger it with my trivial program when
> > > > I link it ag
> >
> > > I still don't seem to fully understand what is happening here --
> > > aparently this is triggerable only with old programs linked against
> > > libc.so.5, and I am not able to trigger it with my trivial program when
> > > I link it against old libc.so.5, which just basically does brk() a
5 matches
Mail list logo
