[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Unexpected behavior & Core dumps
From: |
Michael S . Zick |
Subject: |
Unexpected behavior & Core dumps |
Date: |
Sat, 27 Sep 2003 16:43:47 -0500 |
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib
-g -O2
uname output: Linux wolf686 2.4.20 #2 SMP Sat Apr 12 13:49:20 CDT 2003 i686
unknown
Machine Type: i686-pc-linux-gnu
Bash Version: 2.05b
Patch Level: 0
Release Status: release
Configuration: --enable-static-link --without-gnu-malloc
Description:
Multiple examples. Appears to be only a few problems.
(1) After: unset IFS, IFS may not be redefined and initialized from
a variable. Define and initialize from a literal works.
(2) Parser state error(s) demonstrated by:
${VarName- FuncInvoke} and ${VarName:- FuncInvoke} broke
${VarName+ FuncInvoke} and ${VarName:+ FuncInvoke} works
${SparseArray='Literal'} walks array expecting element to
contain a command.
(3) Everything else involves sparse arrays
Inconsistant element counting;
${#SparseArray[@]} counts content and null-content elements
${SparseArray[@]:Digit:Digit} counts content elements only
(4) Various and sundray core-dump constructs when used on sparse arrays.
Repeat-By:
Commented script attached. Demonstrates what works, what works in an
unexpected way and what core dumps.
Not demonstrated: "assert failure, trying to free an already freed..."
Sorry, I lost track of what caused this more specific error message.
Demo script also contains some wish-list items at appropriate places.
Fix:
Section not included.
)<
Non-Mailing-List subscribed.
Mike
basics_reviewed.bash.bz2
Description: Bug Demo
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Unexpected behavior & Core dumps,
Michael S . Zick <=