Re: Issue with Bash

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Issue with Bash
Date	2020-07-20 08:59 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.225.1595249962.24492.bug-bash@gnu.org> (permalink)
References	<e98f31b4-66a6-46a4-5a05-ad10c98c2f07@case.edu> <OF94D9117F.783D1B7F-ON002585A0.002B581F-002585A0.0033083D@notes.na.collabserv.com> <AM0PR0202MB3442338FB2BA03CC53BF18F5EA640@AM0PR0202MB3442.eurprd02.prod.outlook.com> <OFDCE7FFF8.B623ABC2-ON002585AB.0023ACB2-002585AB.0023F29F@notes.na.collabserv.com> <f5eb0eab-77e9-d5e3-2829-c6275008ddf4@case.edu>

Show all headers | View raw

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 calling readline and whether that's intended.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Issue with Bash Chet Ramey <chet.ramey@case.edu> - 2020-07-20 08:59 -0400

csiph-web