Hello, On Mon, Jun 23, 2008 at 07:55:55PM +0200, Ralf Wildenhues wrote: > [ quoting generously; Vladimir may not be subscribed ]
sorry, Vladimir, that I forgot to cc you. > Vladimir, can you post the md5sum of the script [...] No need to do that, see below. > * Stepan Kasal wrote on Mon, Jun 23, 2008 at 04:43:29PM CEST: > > #!/bin/sh > > as_echo='printf %s\n' > > echo=`$as_echo '\a\b\c\f\n\r\t\v\"\'` > > > > Generally, I tend to think that you have discovered a bug in (your > > version of) bash, not in the Autoconf. > > Except that I cannot reproduce the issue with the same shell. Woo hoo! I can! No, seriously, I also failed to reproduce the problem yesterday. I just supposed I'm supplying enough hints for Vladimir. ;-) But your innocent (was it?) comment has made me to try harder. The original post mentions slamd64, so I downloaded http://slamd64.wahlfaelschung.de/slamd64-current/slackware/a/bash-3.1.017-x86_64_slamd64-2.tgz and was able to reproduce the bug with the binary inside. Then I tried the same with bash-3.1.017-i486-2.tgz from slackware and, again, I was able to reproduce the bug. This bug should be reported. I filed a request for an account in bugzilla bugs.slamd64.com, no response yet. I wasn't able to find any bug report addres nor bug database for slackware. Vladimir, could you please report the bug (with the two-line reproducer quoted above) to the distributions? Thanks, Stepan Kasal
