[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: Regression in ash (crashing)
From:       Rich Felker <dalias () aerifal ! cx>
Date:       2012-12-23 20:18:18
Message-ID: 20121223201818.GB20323 () brightrain ! aerifal ! cx
[Download RAW message or body]

On Tue, Dec 18, 2012 at 09:15:07PM -0500, Rich Felker wrote:
> On Mon, Dec 17, 2012 at 11:29:25AM +0400, Leonid Lisovskiy wrote:
> > On Sat, Dec 15, 2012 at 9:23 PM, Rich Felker <dalias@aerifal.cx> wrote:
> > > On Sat, Dec 15, 2012 at 12:45:13PM +0300, Leonid Lisovskiy wrote:
> > >> Probably we should create bug report with reproducible minimal test-cases?
> > >
> > > Yes and no. It would be nice to have an example case that shows why
> > > the stunalloc is not valid, but I'm not convinced that a test-case is
> > > relevant to fixing the bug. The fix for the present bug is jsut
> > > revering the commit that added it. That brings back the memory-leak
> > > bug, and fixing the memory leak is a more complicated issue, but I
> > > don't think the test-case for the present bug is helpful in fixing the
> > > memory leak..
> > >
> > > If you think I'm wrong on this, please explain why.
> > 
> > The single reason to create bug report with test case is to convince
> > busybox maintainers to revert commit 4ba6c5d3ba.
> 
> OK. Do you think you can come up with one? I tried writing a naive one
> and couldn't get it to crash. It may be better to start with the
> crashing configure script and simplify until it no longer crashes...

I just filed a bug report on the tracker, bug # 5822:

https://bugs.busybox.net/show_bug.cgi?id=5822

Considering that musl's configure script is already small and can be
run outside of the musl source tree, I think making a simplified test
case is fairly low priority. This thread and the report I filed on the
bug tracker document the issue perfectly well. Hopefully somebody will
take notice and fix it soon...

Rich


_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]