this is "asdf{backspace}"
/hdd/newscript # ./hush
/hdd/newscript # asdfhush:
bbbb=00 08 08 08 (0x15b4c7f)
hush:
bbbb=00 08 08 08 (0x15b4c7f)
this is "asdf{cursor left}"
/hdd/newscript # asdfhush:
bbbb=00 08 08 08 (0x15b4c7f)
this is "asdf{home}"
/hdd/newscript # asdfhush:
bbbb=2a 73 00 00 (0x15b4c7c)
*s
(yes, the *s is also from console)
i also did compile with new toolchain (its the same but now i use)
it has the same results
arm-uclinuxtest-elf-gcc -v
Reading specs from
/usr/local/cross-arm/trial/3.4.6/20080205/lib/gcc/arm-uclinuxtest-elf/3.4.6/
specs
Configured with:
/newtool/lastworking/gcc-3.4.6/configure --target=arm-uclinuxtest-elf --pref
ix=/usr/local/cross-arm/trial/3.4.6/20080205 --enable-languages=c --enable-m
ultilib --enable-target-optspace --with-gnu-ld --disable-nls --disable-__cxa
_atexit --disable-c99 --disable-clocale --disable-c-mbchar --disable-long-lo
ng --disable-checking --enable-threads=posix --disable-libstdcxx-pch --enabl
e-cxx-flags=-D_ISOC99_SOURCE -D_BSD_SOURCE
Thread model: posix
gcc version 3.4.6
with
uClibc-0.9.28.3:
the one i was using is:
arm-uclinux-elf-gcc -v
Reading specs from
/usr/local/cross-arm/20050902/bin/../lib/gcc/arm-uclinux-elf/3.4.3/specs
Configured with:
/newtoolchain/gcc-3.4.3/configure --target=arm-uclinux-elf --prefix=/usr/loc
al/cross-arm/20070902 --enable-languages=c,c++ --enable-multilib --enable-ta
rget-optspace --with-gnu-ld --disable-nls --disable-__cxa_atexit --disable-c
99 --disable-clocale --disable-c-mbchar --disable-long-long --disable-checki
ng --enable-threads=posix --disable-libstdcxx-pch --enable-cxx-flags=-D_ISOC
99_SOURCE -D_BSD_SOURCE
Thread model: posix
gcc version 3.4.3
with
uClibc-0.9.26
> -----Oorspronkelijk bericht-----
> Van: Denys Vlasenko [mailto:[EMAIL PROTECTED]
> Verzonden: maandag 18 februari 2008 1:04
> Aan: Martinb_ARM_NOMMU_KISSDVD
> CC: [email protected]
> Onderwerp: Re: Command line editing give a wrong result for me on
> hush shell 1.9.1
>
>
> On Sunday 17 February 2008 20:00, Martinb_ARM_NOMMU_KISSDVD wrote:
> > file is attach
> > wrong (other) results
> >
> > I don't see any garbage but the backspace act (almost) like
> {cursor right}
> > I can send a strace but I'm not sure if it is useful
>
> No, strace is not needed. Now we know where the problem is.
>
> > probably stupid suggestion but if the is a complex problem isn't wise to
> > first find out where the problem start?
> > I can try to use a newer uclibc on my crosscompiler (0.9.28.3
> is the latest
> > I get working) ?
> > if its a NOMMU problem then it should be able to reproduce
>
> Yes, worth trying.
>
> Also please try this: add yet another line - one with bb_error_msg:
>
> if (cmdedit_x >= num) {
> const char *bbbb = "\b\b\b\b";
> cmdedit_x -= num;
> if (num <= 4) {
> bbbb -= num;
> asm volatile("# HERE");
> bb_error_msg("\n bbbb=%02x %02x %02x %02x (%p)", bbbb[0],
> bbbb[1], bbbb[2], bbbb[3], bbbb);
> printf(bbbb);
> return;
> }
> printf("\033[%uD", num);
> return;
> }
>
> It will mess up display when you press Backspace, it's expected.
> I need to know what values will be printed after "bbbb=".
> --
> vda
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox
