Re: Bash-4.3 Official Patch 30

2014-10-08 Thread Andreas Schwab
Chet Ramey writes: > Yes, that's right. The question is whether that case of the index out > of bounds should continue to return NULL, but in a clearer way, or > return "" to differentiate it from the case where shell_input_line is > NULL. Do you need that difference? The only caller treats th

Re: bash uses tmp files for inter-process communication instead of pipes?

2014-10-08 Thread Greg Wooledge
On Tue, Oct 07, 2014 at 03:03:43PM -0700, Linda Walsh wrote: > It's not thoroughly polished yet, but it does work. It can rename and > reorder your > network interfaces on boot so you can keep them with consistent names and > ordering -- something systemd doesn't seem to support. I don't know S

Re: Bash-4.3 Official Patch 30

2014-10-08 Thread Chet Ramey
On 10/8/14, 4:03 AM, Andreas Schwab wrote: > Chet Ramey writes: > >> Yes, that's right. The question is whether that case of the index out >> of bounds should continue to return NULL, but in a clearer way, or >> return "" to differentiate it from the case where shell_input_line is >> NULL. > >

Re: bash using unknown tmp - library based? static link on linux? (was Re: bash not using pipes or /tmp @ boot?)

2014-10-08 Thread Chet Ramey
On 10/8/14, 1:17 AM, Linda Walsh wrote: >>> Yeah... where? >> >> Wherever $TMPDIR says to. If $TMPDIR doesn't name a writable directory, >> bash looks for various system definitions (P_tmpdir), finally defaulting >> to /tmp or /var/tmp. > > P_tmpdir? in ENV? No. P_tmpdir is a #define

locale-dependent token separator handling doesn't work in multi-byte locales

2014-10-08 Thread Stephane Chazelas
When bash parses code it honours the "blank" character class in the current locale as token separator. For instance, if "x" is a blank character in the current locale, echoxbar would output bar. "yash" is the only other shell that I know that does the same. With bash, that only works in single-

Re: locale-dependent token separator handling doesn't work in multi-byte locales

2014-10-08 Thread Eric Blake
On 10/08/2014 08:52 AM, Stephane Chazelas wrote: > When bash parses code it honours the "blank" character class in > the current locale as token separator. > > For instance, if "x" is a blank character in the current locale, Such a locale is invalid per POSIX; but the invalidity of the locale doe

Re: locale-dependent token separator handling doesn't work in multi-byte locales

2014-10-08 Thread Chet Ramey
On 10/8/14, 10:52 AM, Stephane Chazelas wrote: > When bash parses code it honours the "blank" character class in > the current locale as token separator. Posix requires it. > With bash, that only works in single-byte locales though. > Probably because bash does some isblank() on individual bytes

Re: locale-dependent token separator handling doesn't work in multi-byte locales

2014-10-08 Thread Stephane Chazelas
2014-10-08 09:17:18 -0600, Eric Blake: [...] > I would argue that locale-dependent parsing is probably a bug waiting to > happen, and would be in favor of removing the feature and forcing the > use of the C locale for the duration of parsing a script. Yes, that > means you can't write a variable n

Adding a new configure option to enable/disable getenv redefinition

2014-10-08 Thread Vicente Olivert Riera
Hello, when bash is being cross-compiled it can't detect if getenv can be redefined... configure:14432: checking to see if getenv can be redefined configure:14438: WARNING: cannot check getenv redefinition if cross compiling -- defaulting to yes configure:14489: result: yes ...so it defaults

Re: locale-dependent token separator handling doesn't work in multi-byte locales

2014-10-08 Thread Ángel González
Eric Blake wrote: > On 10/08/2014 08:52 AM, Stephane Chazelas wrote: > > When bash parses code it honours the "blank" character class in > > the current locale as token separator. > > > > For instance, if "x" is a blank character in the current locale, > > Such a locale is invalid per POSIX; but

Re: Adding a new configure option to enable/disable getenv redefinition

2014-10-08 Thread Eric Blake
On 10/08/2014 08:30 AM, Vicente Olivert Riera wrote: > Hello, > > when bash is being cross-compiled it can't detect if getenv can be > redefined... > > What do you think about adding a new configure option like > "--with-getenv=yes|no" to explicitly state if getenv has to be redefined? It alrea

Re: locale-dependent token separator handling doesn't work in multi-byte locales

2014-10-08 Thread Eric Blake
On 10/08/2014 11:53 AM, Ángel González wrote: > Eric Blake wrote: >> On 10/08/2014 08:52 AM, Stephane Chazelas wrote: >>> When bash parses code it honours the "blank" character class in >>> the current locale as token separator. >>> >>> For instance, if "x" is a blank character in the current local

Re: bash using unknown tmp - library based? static link on linux? (was Re: bash not using pipes or /tmp @ boot?)

2014-10-08 Thread Linda Walsh
Chet Ramey wrote: On 10/8/14, 1:17 AM, Linda Walsh wrote: P_tmpdir? in ENV? No. P_tmpdir is a #define in stdio.h that holds the full pathname of the compilation environment's preferred temporary directory. I don't have TMP or TMPDIR in my env during normal runtime and tmp's were put in /

Bash 4.3 with patch 29 causing segfault during ./configure when trying to upgrade to patch 30

2014-10-08 Thread jon
dmesg. [307688.764489] configure[25847]: segfault at 9558104 ip 080e2246 sp bfd478f0 error 4 in bash[8048000+148000] [307689.436739] configure[25966]: segfault at 95580b4 ip 080e2246 sp bfd478f0 error 4 in bash[8048000+148000] [307689.467279] configure[25983]: segfault at 9558104 ip 080e2246