Re: [bash4.2] ${v//[/} bug?

[Allan McRae]

On 16/02/11 11:20, Chet Ramey wrote:

On 2/15/11 6:18 AM, Clark J. Wang wrote:

For following script:

var='[hello'
echo "${var//[/}"

With bash 4.1 it outputs hello but with 4.2 it outputs [hello . And bash 4.2
with compat41 on still outputs [hello . Bug? Or Bug fixed?


This is strange.  It echoes "hello" on Mac OS X, but "[hello" on
Red Hat.  I'll have to take a look at where the difference might be.



Just to rule out it being Linux specifc, I get the expected "hello" on 
Arch Linux.


Allan

Re: Bash-4.2 Official Patch 5

[Allan McRae]

On 01/03/11 11:58, Chet Ramey wrote:

BASH PATCH REPORT
 =

Bash-Release:   4.2
Patch-ID:   bash42-005

Bug-Reported-by:Dennis Williamson
Bug-Reference-ID:   

Bug-Reference-URL:  
http://lists.gnu.org/archive/html/bug-bash/2011-02/msg00147.html

Bug-Description:

Systems that use tzset() to set the local timezone require the TZ variable
to be in the environment.  Bash must make sure the environment has been
modified with any updated value for TZ before calling tzset().  This
affects prompt string expansions and the `%T' printf conversion specification
on systems that do not allow bash to supply a replacement for getenv(3).

Patch (apply with `patch -p0'):



This patch just caused some havoc for Arch Linux testing repository 
users who found their systems no longer booted...


Here is one our users findings on the issue:

On 01/03/11 23:57, Evangelos Foutras wrote:
> `unset TZ' is the simplest test case that causes a segmentation fault
> on my system.
>
> The culprit appears to be the chkexport function introduced in patch
> bash42-005 [1]. From the backtrace [2], I gather it should probably
> check that find_variable returns a non-NULL value. Changing the line
> after the find_variable call to read "if (v&&  exported_p (v))" fixes
> the issue for me.


Allan

Re: Bash-4.2 Official Patch 5

[Allan McRae]

On 02/03/11 01:20, Chet Ramey wrote:

On 3/1/11 10:13 AM, Allan McRae wrote:

On 01/03/11 11:58, Chet Ramey wrote:

 BASH PATCH REPORT
  =

Bash-Release:4.2
Patch-ID:bash42-005

Bug-Reported-by:Dennis Williamson
Bug-Reference-ID:

Bug-Reference-URL:
http://lists.gnu.org/archive/html/bug-bash/2011-02/msg00147.html

Bug-Description:

Systems that use tzset() to set the local timezone require the TZ variable
to be in the environment.  Bash must make sure the environment has been
modified with any updated value for TZ before calling tzset().  This
affects prompt string expansions and the `%T' printf conversion
specification
on systems that do not allow bash to supply a replacement for getenv(3).

Patch (apply with `patch -p0'):



This patch just caused some havoc for Arch Linux testing repository users
who found their systems no longer booted...

Here is one our users findings on the issue:

On 01/03/11 23:57, Evangelos Foutras wrote:

`unset TZ' is the simplest test case that causes a segmentation fault
on my system.

The culprit appears to be the chkexport function introduced in patch
bash42-005 [1]. From the backtrace [2], I gather it should probably
check that find_variable returns a non-NULL value. Changing the line
after the find_variable call to read "if (v&&   exported_p (v))" fixes
the issue for me.


Here's a quick patch.  Give it a workout.



From a brief test, everything seems fine with that patch.  Well, at 
least my system continued to boot!


Thanks,
Allan

UTF8 conversion issues in bash-4.2

[Allan McRae]

I am seeing what appears to be some sort of UTF-8 conversion issue in 
bash-4.2.  I do not see this in bash 4.1.   I think the easiest way to 
describe this is:



> bash41 --version
GNU bash, version 4.1.9(2)-release (i686-pc-linux-gnu)

> LC_ALL=ru_RU.UTF-8 bash41 -c привет
bash: привет: command not found


> bash42 --version
GNU bash, version 4.2.8(2)-release (i686-pc-linux-gnu)

> LC_ALL=ru_RU.UTF-8 bash42 -c привет
bash: $'\320\277\321\200\320\270\320\262\320\265\321\202': команда не 
найдена


> LC_ALL=ru_RU.KOI8-R bash42 -c привет
bash: привет: ��� �� ��


I'm not sure what further information is needed here, so let me know if 
you need anything else to replicate this.


Allan

Re: Bash-4.2 patches 9 and 10

[Allan McRae]

On 13/05/11 21:44, Eric Blake wrote:

On 05/13/2011 04:54 AM, Joachim Schmitz wrote:

Hi folks

Just found Bash-4.2 patches 9 and 10, strange that they never got
announced?


Yes they did:

http://lists.gnu.org/archive/html/bug-bash/2011-05/msg00014.html
http://lists.gnu.org/archive/html/bug-bash/2011-05/msg00015.html

Along with an accidental announcement for a missing patch 11:

http://lists.gnu.org/archive/html/bug-bash/2011-05/msg00028.html




Patch 11 was for 4.1
http://ftp.gnu.org/gnu/bash/bash-4.1-patches/