On 6/21/17 6:01 PM, Kevin Brodsky wrote:
> On 21/06/2017 20:29, Chet Ramey wrote:
>> On 6/21/17 2:43 PM, Kevin Brodsky wrote:
>>
>>> That is also my reading of POSIX (and that's more or less what Bash's
>>> manpage says as well), but it doesn't seem to be the case (even in <=4.2):
>> That's a relat
On 21/06/2017 20:29, Chet Ramey wrote:
> On 6/21/17 2:43 PM, Kevin Brodsky wrote:
>
>> That is also my reading of POSIX (and that's more or less what Bash's
>> manpage says as well), but it doesn't seem to be the case (even in <=4.2):
> That's a relatively new requirement. The portion of the relev
On 6/21/17 2:43 PM, Kevin Brodsky wrote:
> That is also my reading of POSIX (and that's more or less what Bash's
> manpage says as well), but it doesn't seem to be the case (even in <=4.2):
That's a relatively new requirement. The portion of the relevant sentence
that reads "initially producing
On 21/06/2017 14:54, Chet Ramey wrote:
> On 6/20/17 1:33 AM, Eduardo A. Bustamante López wrote:
>> On Tue, Jun 20, 2017 at 01:13:07AM +0100, Kevin Brodsky wrote:
>> [...]
>>> When IFS is unset, unquoted $* undergoes word splitting as if IFS=' ',
>>> and not the expected IFS=$' \t\n'. All the other
need to use strncmp for relative path check:
if (!strncmp (s, "/./", 3) || !strncmp (s, "/../", 4))
{
++s;
}
On Wed, Jun 21, 2017 at 8:53 AM, Zartaj Majeed wrote:
> This update to the patch adds the following:
>
> 1. Check socket file path length less than sizeof sun_path array in
> s
On 6/20/17 1:33 AM, Eduardo A. Bustamante López wrote:
> On Tue, Jun 20, 2017 at 01:13:07AM +0100, Kevin Brodsky wrote:
> [...]
>> When IFS is unset, unquoted $* undergoes word splitting as if IFS=' ',
>> and not the expected IFS=$' \t\n'. All the other unquoted mass
>> This is a regression that ap
On 6/19/17 8:13 PM, Kevin Brodsky wrote:
> Hi,
>
> When IFS is unset, unquoted $* undergoes word splitting as if IFS=' ',
> and not the expected IFS=$' \t\n'. All the other unquoted mass
> expansions ($@, array[*], array[@]) are word-split as if IFS=$'
> \t\n'.
Thanks for the report. This will be
On 6/20/17 1:06 AM, Eduardo A. Bustamante López wrote:
> There's something weird about the wait builtin + SIGINT handling in the latest
> `devel' branch (i.e. 6374eecf232e70e45fe9c49cc8335e8779c07979)
Well, that comment in the code certainly proved out. Thanks for the report.
Chet
--
``The lyf
This update to the patch adds the following:
1. Check socket file path length less than sizeof sun_path array in
struct sockaddr_un
2. Allow relative socket file paths starting with "./" or "../". This
means the pseudo filename
opened in bash is of the form "/dev/unixstream/./xyz.sock" or
"/dev/un
On Tue, 2017-06-20 at 23:47 -0500, Eduardo A. Bustamante López wrote:
> On Tue, Jun 20, 2017 at 11:49:56AM -0400, tetsu...@scope-eye.net wrote:
> [...]
> >
> > So implementing Unix Domain Sockets in the shell would give you the
> > ability to connect to existing services on the machine that use na
Hi,
No this is an occasional issue and there is no reproducer yet.
Regards,
Mukunth
-Original Message-
From: Eduardo Bustamante [mailto:dual...@gmail.com]
Sent: Tuesday, June 20, 2017 9:12 PM
To: Rajaa, Mukuntha (Nokia - IN/Bangalore)
Cc: bug-bash@gnu.org
Subject: Re: bash sigabrt
On
11 matches
Mail list logo
