On Wed, 4 Feb 2009, Cristian Ionescu-Idbohrn wrote:
> On Wed, 4 Feb 2009, Denys Vlasenko wrote:
>
> > On Tuesday 03 February 2009 20:43, Cristian Ionescu-Idbohrn wrote:
> > > On Sat, 31 Jan 2009, Denys Vlasenko wrote:
> > >
> > > > if (p==NULL) bb_error_msg("p is NULL at %d!", __LINE__)
> > > > ========> expdest = stack_nputstr(p, length, expdest);
> > >
> > > None of the CONFIG_ tweaks led to anything catchable. It's a moving
> > > target :(
> > >
> > > > Let me know what do you see.
> > >
> > > Though, I managed to isolate the problem to the transition from 1.11.3
> > > where ash doesn't segfault in the tested environment, to 1.12.0 (with
> > > applied fixes).
> >
> > So, busybox-1.12.4 (latest 1.12.x) segfaults.
> >
> > Does busybox-1.12.4 with the attached patch reverted works?
> > It should, because this patch returns ash.c to 1.11.3 state.
>
> I see what you mean.
> 1.12.4 with the named patch applied segfaults :(
>
> So, we're left with the suspicion something under the 'libbb'
> directory may contribute to my problem.
Obviously may 'include/*' be also a plausible candidate.
Cheers,
--
Cristian
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
