This was in the 2nd half of the note in the read&env+POSIX=>SEGFAULT,
but think it got missed by focus on the 1st part.
# I was doing some syntax testing and decided to try posix mode
# (as it disallows various vague or unclear constructs)
# in the working cases yielded the same results, but
# in 2 cases it returned a SEGFAULT.
b= mapfile b <<< x; echo $?
0
declare -p b
Segmentation fault (core dumped)
# another example of bash not returning consistent errno results
# ( |;>| ducking while smirking) ok, I vote for disallowing this
# type of result return.
The 2nd flavor:
b= mapfile b a <<< x
declare -p a b
bash: declare: a: not found
Segmentation fault (core dumped)
# odd, this time it dumped on printing 'b'; still not so great
# status returning there...
# hmmm... I'm guessing that fixing these to not return
# segfaults won't be likely to get me better status
# returns for my type -P problems....*sigh*
# vitals:
$0 --version
GNU bash, version 4.3.39(1)-release (x86_64-unknown-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.