Re: Issue with Bash

2020-08-02 Thread Chet Ramey
On 7/31/20 7:27 PM, Ángel wrote: > On 2020-07-31 at 10:13 -0400, Chet Ramey wrote: >> >> I'm going to have to test some more. When I tried it, all the shells >> died. >> (I did send the SIGHUP from another terminal.) I was using ksh93 as >> the parent and bash-5.0.18 as the interactive bash, runnin

Re: Issue with Bash

2020-08-02 Thread Chet Ramey
On 7/31/20 10:04 AM, Ayappan P2 wrote: > We are passing SIGHUP from another terminal ( not from the terminal which > has the interactive bash shell) . The terminal which has the interactive > bash closes immediately. > > The scenario is we just open two terminals. In one terminal , just invoke > b

Re: Issue with Bash

2020-07-31 Thread Ángel
On 2020-07-31 at 10:13 -0400, Chet Ramey wrote: > > I'm going to have to test some more. When I tried it, all the shells > died. > (I did send the SIGHUP from another terminal.) I was using ksh93 as > the parent and bash-5.0.18 as the interactive bash, running on macOS. This is probably AIX-speci

Re: Issue with Bash

2020-07-31 Thread Chet Ramey
On 7/31/20 10:04 AM, Ayappan P2 wrote: > We are passing SIGHUP from another terminal ( not from the terminal which > has the interactive bash shell) . The terminal which has the interactive > bash closes immediately. > > The scenario is we just open two terminals. In one terminal , just invoke > b

RE: Issue with Bash

2020-07-31 Thread Ayappan P2
the parent process (ksh) of bash. Thanks Ayappan P From: Chet Ramey To: Rishita Saha16 Cc: bug-bash@gnu.org, chet.ra...@case.edu Date: 31-07-2020 19:05 Subject:[EXTERNAL] Re: Issue with Bash Sent by:"bug-bash" On 7/31/20 3:25 AM, Rishita Saha16 wrote

Re: Issue with Bash

2020-07-31 Thread Chet Ramey
On 7/31/20 3:25 AM, Rishita Saha16 wrote: > Hi All, >   > We have been able to recreate a scenario where bash dumps core immediately > on issuing a SIGHUP to the parent process (kill -1 ). On > debugging, the core so generated shows exactly the same stack trace as we > had seen with the previous co

RE: Issue with Bash

2020-07-31 Thread Rishita Saha16
] Re: Issue with Bash Date: Mon, Jul 20, 2020 6:29 PM On 7/20/20 2:32 AM, Rishita Saha16 wrote: > Hi All, > > From what we have found out, it does not seem like the signal is SIGTTOU. > We are working to find out more about it. Meanwhile, any insight would be

Re: Issue with Bash

2020-07-20 Thread Chet Ramey
On 7/20/20 2:32 AM, Rishita Saha16 wrote: > Hi All, >   > From what we have found out, it does not seem like the signal is SIGTTOU. > We are working to find out more about it. Meanwhile, any insight would be > helpful. If the process isn't an interactive shell, it would be helpful to know why it's

RE: Issue with Bash

2020-07-19 Thread Rishita Saha16
HIGOT, CLEMENT" , Rishita Saha16 , "bug-bash@gnu.org" Cc: chet.ra...@case.edu Subject: [EXTERNAL] Re: Issue with Bash Date: Thu, Jul 9, 2020 8:01 PM On 7/9/20 10:16 AM, CHIGOT, CLEMENT wrote: > Hi Rishita, > > Could you try with BullFreeware

Re: Issue with Bash

2020-07-10 Thread CHIGOT, CLEMENT
riday, July 10, 2020 1:40 PM To: CHIGOT, CLEMENT Cc: bug-bash@gnu.org Subject: RE: Issue with Bash Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe. Hi Clement, We have given it a try after applyin

RE: Issue with Bash

2020-07-10 Thread Rishita Saha16
Cc: Subject: [EXTERNAL] Re: Issue with Bash Date: Thu, Jul 9, 2020 7:46 PM Hi Rishita, Could you try with BullFreeware's version, which have a slightly higher version (5.0.11 instead of 5.0) ? You can find it at [1]http://www.bullfreeware.com/pkg?id=5740. If it&

Re: Issue with Bash

2020-07-09 Thread Chet Ramey
On 7/9/20 10:16 AM, CHIGOT, CLEMENT wrote: > Hi Rishita, > > Could you try with BullFreeware's version, which have a slightly higher > version (5.0.11 instead of 5.0) ? > You can find it at > http://www.bullfreeware.com/pkg?id=5740. > > If it's not worki

Re: Issue with Bash

2020-07-09 Thread CHIGOT, CLEMENT
Hi Rishita, Could you try with BullFreeware's version, which have a slightly higher version (5.0.11 instead of 5.0) ? You can find it at http://www.bullfreeware.com/pkg?id=5740. If it's not working, I'll check what's wrong. Clément _

Re: Issue with Bash

2020-07-09 Thread Chet Ramey
On 7/9/20 5:17 AM, Rishita Saha16 wrote: >Hi All, > >We are using Bash 5.0 (64bit built using gcc ) in AIX 7.2 machine .This >is the spec file for reference --> >[1]https://public.dhe.ibm.com/aix/freeSoftware/aixtoolbox/SPECS/bash-5. >0-1.spec. >We are seeing recurring bash

Re: Issue with Bash-4.3 Official Patch 27

2014-10-17 Thread Chet Ramey
On 10/17/14, 11:34 AM, Greg Wooledge wrote: > 3) Everything else. These are ignored. > Not quite. Bash saves them and adds them to the environment it passes to the external commands it invokes. Bash is transparent with respect to environment variables it doesn't handle. Chet -- ``The lyf so

Re: Issue with Bash-4.3 Official Patch 27

2014-10-17 Thread Chet Ramey
On 10/17/14, 11:22 AM, lorenz.bucher@rohde-schwarz.com wrote: > No, I can't. > $ foo%%="bar" > foo%%=bar: command not found You just demonstrated what I wrote: > No, shell variable names should continue to be shell identifiers. You > can already use `%' (any character, really) in environmen

Re: Issue with Bash-4.3 Official Patch 27

2014-10-17 Thread Chet Ramey
On 10/16/14, 4:37 PM, Geir Hauge wrote: > Regardless though, shouldn't source <(declare -xp) work whether or not > the environment contains invalid identifiers? It doesn't at present: > > $ env %=% bash -c 'echo "$BASH_VERSION"; source <(declare -xp)' > 4.3.30(1)-release > /dev/fd/63: line 1: dec

Re: Issue with Bash-4.3 Official Patch 27

2014-10-17 Thread Greg Wooledge
> Von:Chet Ramey > No, shell variable names should continue to be shell identifiers. You > can already use `%' (any character, really) in environment variable > names. On Fri, Oct 17, 2014 at 05:22:30PM +0200, lorenz.bucher@rohde-schwarz.com wrote: > No, I can't. > $ foo%%="bar" > foo%

Re: Issue with Bash-4.3 Official Patch 27

2014-10-17 Thread Lorenz . Bucher . ext
chet.ra...@case.edu Datum: 10/16/2014 03:09 PM Betreff:Re: Issue with Bash-4.3 Official Patch 27 Gesendet von: bug-bash-bounces+lorenz.bucher.ext=rohde-schwarz@gnu.org On 10/15/14, 1:49 PM, lorenz.bucher@rohde-schwarz.com wrote: > But anyway. > In my opinion I should trus

Re: Issue with Bash-4.3 Official Patch 27

2014-10-16 Thread Geir Hauge
2014-10-16 15:09 GMT+02:00 Chet Ramey : > On 10/15/14, 1:49 PM, lorenz.bucher@rohde-schwarz.com wrote: > > > But anyway. > > In my opinion I should trust a shell not violating their own rules and be > > able to import their own variables. > > That's not the issue. The shell can import variabl

Re: Issue with Bash-4.3 Official Patch 27

2014-10-16 Thread Chet Ramey
On 10/15/14, 1:49 PM, lorenz.bucher@rohde-schwarz.com wrote: > But anyway. > In my opinion I should trust a shell not violating their own rules and be > able to import their own variables. That's not the issue. The shell can import variables like that just fine, as evidenced by exported fun

Re: Issue with Bash-4.3 Official Patch 27

2014-10-16 Thread Chet Ramey
On 10/15/14, 9:38 AM, lorenz.bucher@rohde-schwarz.com wrote: > Hello, > in refer to > http://lists.gnu.org/archive/html/bug-bash/2014-09/msg00278.html variables > with suffix "%%" can't be set/exported. > This makes problems restoring environments which where saved by external > programs lik

Re: Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Eric Blake
On 10/15/2014 11:49 AM, lorenz.bucher@rohde-schwarz.com wrote: > Yes, you got it. I just gave an example to reproduce that Bug. In my case > I didn't find the save script/binary yet. > I use unset -f function as workaround. > > But anyway. > In my opinion I should trust a shell not violatin

Re: Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Lorenz . Bucher . ext
o the % character should be allowed to be used in variable names. Von:Greg Wooledge An: Eduardo A. Bustamante López , Kopie: lorenz.bucher@rohde-schwarz.com, bug-bash@gnu.org Datum: 10/15/2014 05:58 PM Betreff: Re: Issue with Bash-4.3 Official Patch 27 On Wed, Oct 15, 2014 at

Re: Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Steve Simmons
On Oct 15, 2014, at 9:38 AM, lorenz.bucher@rohde-schwarz.com wrote: > Hello, > in refer to > http://lists.gnu.org/archive/html/bug-bash/2014-09/msg00278.html variables > with suffix "%%" can't be set/exported. > This makes problems restoring environments which where saved by external > prog

Re: Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Greg Wooledge
On Wed, Oct 15, 2014 at 08:50:25AM -0700, Eduardo A. Bustamante López wrote: > On Wed, Oct 15, 2014 at 03:38:01PM +0200, lorenz.bucher@rohde-schwarz.com > wrote: > > variables with suffix "%%" can't be set/exported. > > This makes problems restoring environments which where saved by external

Re: Issue with Bash-4.3 Official Patch 27

2014-10-15 Thread Eduardo A . Bustamante López
On Wed, Oct 15, 2014 at 03:38:01PM +0200, lorenz.bucher@rohde-schwarz.com wrote: > Hello, > in refer to > http://lists.gnu.org/archive/html/bug-bash/2014-09/msg00278.html variables > with suffix "%%" can't be set/exported. > This makes problems restoring environments which where saved by ext