> >
> > > 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() and
> > > checks whether /proc/<pid>/maps are OK. Seems to me that (at least
> > > certain versions) of libc.so.5 (wrongly) assume that end of the bss is
> > > the start of the heap, but I will try to investigate it more.
>
> 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 workaround mine by
disabling randomization...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
