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).
My upgrade path was from 1.11.2 to 1.13.2, that's why I did not notice the
problem earlier.
Interesting to note is also that compiler optimisation matters. Building
with -O0 or O1 does not produce segfaults. Building with -O2 _does_.
Cheers,
--
Cristian
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
