BASH PATCH REPORT
=
Bash-Release: 4.3
Patch-ID: bash43-031
Bug-Reported-by:lolilolicon
Bug-Reference-ID:
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-bash/2014-08/msg00139.html
Bu
BASH PATCH REPORT
=
Bash-Release: 4.3
Patch-ID: bash43-032
Bug-Reported-by:crispusfairba...@gmail.com
Bug-Reference-ID:
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-bash/2014-09/msg0
BASH PATCH REPORT
=
Bash-Release: 4.3
Patch-ID: bash43-033
Bug-Reported-by:micka...@gmail.com, Jan Rome
Bug-Reference-ID: <20140907224046.382ED3610CC@mickael-laptop.localdomain>,
Hello.
I often use "set -eu" to make my scripts more robust by exiting when
there are errors.
But one of my scripts just kept on running after failures. I found out
that the keyword "local" does not obey it. Here is a script to
reproduce the problem:
#!/bin/bash
set -eu
failure() {
echo "g
On Tue, Dec 30, 2014 at 02:03:01PM +0200, Ville Oikarinen wrote:
> I often use "set -eu" to make my scripts more robust by exiting when
> there are errors.
http://mywiki.wooledge.org/BashFAQ/105
> But one of my scripts just kept on running after failures. I found out
> that the keyword "local" do
On 12/30/14 7:03 AM, Ville Oikarinen wrote:
> Hello.
>
> I often use "set -eu" to make my scripts more robust by exiting when
> there are errors.
>
> But one of my scripts just kept on running after failures. I found out
> that the keyword "local" does not obey it. Here is a script to
> reproduce
Hello,
got the following issue with patch 31 on a CRUX Linux system with
gcc 4.8.4:
gcc -DPROGRAM='"bash"' -DCONF_HOSTTYPE='"x86_64"' -DCONF_OSTYPE='"linux-gnu"'
-DCONF_MACHTYPE='"x86_64-unknown-linux-gnu"' -DCONF_VENDOR='"unknown"'
-DLOCALEDIR='"/usr/share/locale"' -DPACKAGE='"bash"' -DSHELL
On 12/30/14 10:01 AM, Juergen Daubert wrote:
> Hello,
>
> got the following issue with patch 31 on a CRUX Linux system with
> gcc 4.8.4:
I wonder why clang didn't catch that. I will fix it.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita
On 12/30/14 10:01 AM, Juergen Daubert wrote:
> Hello,
>
> got the following issue with patch 31 on a CRUX Linux system with
> gcc 4.8.4:
Try this one.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU
BASH PATCH REPORT
=
Bash-Release: 4.3
Patch-ID: bash43-031
Bug-Reported-by:lolilolicon
Bug-Reference-ID:
Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-bash/2014-08/msg00139.html
Bu
On Tue, Dec 30, 2014 at 10:12:35AM -0500, Chet Ramey wrote:
> On 12/30/14 10:01 AM, Juergen Daubert wrote:
> > Hello,
> >
> > got the following issue with patch 31 on a CRUX Linux system with
> > gcc 4.8.4:
>
> Try this one.
>
Thanks, builds again.
> Cool, another one to add to the wiki page! I am always excited by new
> weapons in the never-ending war against set -e.
>
> This particular issue was also already noted in a more general context on
> http://mywiki.wooledge.org/BashPitfalls -- see entry #27.
Ah, so there is a "workaround", thank
12 matches
Mail list logo