On Wed, Nov 25, 2009 at 05:56:02PM +0100, walter harms wrote: >hi list, >i am still trying to find the bug but i noted something more disturbing. >With the move from 1.14.4 to 1.15.0 i found that my startup started sending a >bunch >of 0 bytes to the terminal. This is gone unnoticed so far as that we do not >see the hexvalues >of the startupmessages. (i used them to see the bug above). >It would be nice if someone would check that so i can get a second opinion. > >I strongly suspect ash.c for the above behavior as that replacing the 1.15.2 >ash.c with >1.15.1 restores the old bug. Please note that system look perfectly normal >when you only >look at the ascii dump, i experience a crash only with 1.15.2. > >I have still no idea if the bug is inside the toolchain or busybox.
-) So what arch, binutils, gcc (eventual EXTRA_CFLAGS), patches are you using? -) build with -O0, verify if the bug is still there >re, > wh > >example output: 1.15.0 with block of 0 > >0015f80: 653a 2035 2028 636c 6f63 6b20 6e6f 7420 e: 5 (clock not >0015f90: 7379 6e63 6872 6f6e 697a 6564 290d 0a00 synchronized)... >0015fa0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ >...... >0017e20: 0000 0000 0000 0000 0000 0000 0000 0000 ................ >0017e30: 0000 0000 0000 0000 0000 0000 2a2a 2a2a ............**** >0017e40: 2a2a 2a2a 2a2a 2a2a 2a2a 2a2a 2a2a 2a2a **************** > > > > > > > > > > > >_______________________________________________ >busybox mailing list >[email protected] >http://lists.busybox.net/mailman/listinfo/busybox _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
