John Malmberg - 2013-06-14

When you run find from DCL, what is expanding the *?

When you run find from bash, bash should be expanding the wildcard making the command line different.

An error in malloc() from a call to readdir() indicates either we have a heap corruption in the find utility or a bug in the CRTL.

This is what I get using the find from GNV 2.1.3 on Alpha and the bash 4.2.45(1) in development.

BASH-4.2$ find . -iname config.*
find: paths must precede expression
Usage: find [path...] [expression]

Dropping the ".*" results in a lot of CPU and IO activity and no files found.

BASH-4.2$ find . -iname config.
find: paths must precede expression
Usage: find [path...] [expression]
BASH-4.2$ find . -iname config
BASH-4.2$ find . -iname 'config
'
./config.h
./config_vms.h
./lib/intl/config.charset
./lib/intl/config.charset
./lib/intl/config.charset
./support/config.guess
./support/config.rpath
./support/config.sub
./config.h_gnv_reference
./config_h.com
./config_vms.h_in
./lib/intl/config.charset
./lib/intl/config.charset
./lib/intl/config.charset
./support/config.guess
./support/config.rpath
./support/config.sub
./config-bot.h
./config-top.h
./config.h.in
./configure
./configure.in
./lib/intl/config.charset
./lib/intl/config.charset
./lib/intl/config.charset
./support/config.guess
./support/config.rpath
./support/config.sub
BASH-4.2$