On Tue, Feb 24, 2009 at 10:38:49PM +0100, Roland Mainz wrote: > Edward Pilatowicz wrote: > > On Wed, Feb 18, 2009 at 01:03:25AM -0500, Glenn Fowler wrote: > > > On Tue, 17 Feb 2009 21:30:48 -0800 Edward Pilatowicz wrote: > [snip] > > > can you run the same test with libumem configured with sbrk() vs mmap()? > > > > hm. i just upgraded my desktop from 106 to 107 and i can't reproduce the > > problem there anymore, but the good news is i can still reproduce it on > > another > > machine running 108. > > Is this a _debug_ build of B108 ? >
yes. > > it doesn't seem to matter if we use mmap or sbrk. > > > > ---8<--- > > edp at jurassic-x4600$ UMEM_OPTIONS=sbrk LC_ALL=en_US.ISO8859-1 /bin/time > > /bin/sleep 1 > > time: command terminated abnormally. > > > > real 3.7 > > user 0.0 > > sys 0.0 > > edp at jurassic-x4600$ UMEM_OPTIONS=mmap LC_ALL=en_US.ISO8859-1 /bin/time > > /bin/sleep 1 > > time: command terminated abnormally. > > > > real 2.3 > > user 0.0 > > sys 0.0 > > ---8<--- > > Does it still happen if you do a $ env - UMEM_OPTIONS=mmap > LC_ALL=en_US.ISO8859-1 /bin/time /bin/sleep 1 # ($ env - ... # clears > the environment) ? > no. because with the above invocation libumem is not loaded. but, i can reproduce the crash with the following invocation: ---8<--- env - LD_PRELOAD=libumem.so UMEM_DEBUG=guards UMEM_OPTIONS=backend=mmap LC_ALL=en_US.ISO8859-1 /bin/time /bin/sleep 1 ---8<---
