Regression in ash (crashing)

[Rich Felker]

On Thu, Dec 13, 2012 at 07:25:11PM +0300, Leonid Lisovskiy wrote:
> > On Wed, Dec 12, 2012 at 02:02:00PM -0500, Rich Felker wrote:
> ....
> > I don't think valgrind is going to be a big help because the invalid
> > alloc/free logic seems to be not at the system malloc level but ash's
> > stack allocator. Is there any way to get ash to just use malloc/free
> > for everything so valgrind can detect the invalid usage pattern?
> 
> Have you turn on --track-origins=yes  --leak-check=yes valgrind options ?

No. I can try investigating further using them, but if you read my
most recent post to this thread, you'll see that I'm fairly certain
the problem is just that the stunalloc operation is fundamentally
impossible at the point it was added in
4ba6c5d3ba3d2c7922aff6b5c2e73b8325f1cf17 due to the nature of the
stack allocator. I don't think this bug is any deeper than that.

Rich