> On 25 Oct 2016, at 17:36, Eduardo Bustamante <dualbus@gmail.com> wrote:
>
> What version of bash are you using Stuart? typeset -p should work for
> local variables too in any recent bash version.
typeset omitting existing variables or failing and causing a SIGPIPE I’ve seen
with Ubuntu 14.04 LTS’ bash-4.3.11(1). The immediately prior example (where
variables declared local but unset in terms of value weren’t causing typeset to
return successfully) was run on Ubuntu 16.10’s bash-4.3.46(1). This later
version doesn’t seem to be affected by the apparently non-deterministic
original problem, however.
I’ve not seen any case where calling typeset again immediately after having
called it and received an anomalous response doesn’t respond correctly - so my
current solution is simply to invoke typeset twice… but the presence of this
discrepancy is worrying.
If this isn’t expected bash-4.3 behaviour, then it’s entirely possible that
Canonical are doing something strange here, of course...