helpThe GNU Bourne-Again SHell - Support: sr #108593, Interrupt on process substitution...

 
 

sr #108593: Interrupt on process substitution from stdin kills bash

Submitted by:  DrkShadow <drkshadow>
Submitted on:  Wed Jun 4 06:38:01 2014  
 
Category: NonePriority: 5 - Normal
Severity: 3 - NormalStatus: Done
Privacy: PublicAssigned to: None
Open/Closed: OpenOperating System: GNU/Linux

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Tue Nov 17 21:37:55 2015, comment #5:

I have figured out why, and will have a fix in place for the next version.

Chet Ramey <chet>
Project Administrator
Mon Nov 16 21:51:24 2015, comment #4:

For an unknown reason, xterm (but not other terminal emulators) sends the parent shell a SIGHUP after the SIGINT, which causes the shell to exit. I'm looking at why that is.

Chet Ramey <chet>
Project Administrator
Sat Nov 14 00:30:25 2015, comment #3:

Talking with another,

this issue doesn't happen in bash inside a bash. I also can't reproduce it in a tty. For me it happens inside screen inside xterm. Another says it happens in xterm and st, but not urxvt. The same person says also that zsh and ksh do not have the issue.

So,
$ xterm bash

$ cat < <(cat)
^C

causes multiple terminals to exit.

DrkShadow <drkshadow>
Wed Mar 25 11:18:21 2015, comment #2:

Not a bug

Cannot reproduce:

dualbus@yaqui ~/t % bash
dualbus@yaqui:~/t$ cat < <(cat)
^C
dualbus@yaqui:~/t$
GNU bash, version 4.3.33(1)-release (x86_64-pc-linux-gnu)
dualbus@yaqui:~/t$ exit
dualbus@yaqui ~/t % ~/local/gnu/bash/devel/bin/bash
dualbus@yaqui:~/t$ cat < <(cat)
^C
dualbus@yaqui:~/t$
GNU bash, version 4.4.0(1)-devel (x86_64-unknown-linux-gnu)

Eduardo Bustamante <dualbus>
Wed Jun 4 06:46:30 2014, comment #1:

Final line did not display:

When you execute and then ctrl-C this command, BASH exits.

DrkShadow <drkshadow>
Wed Jun 4 06:38:01 2014, original submission:

I was executing a command, and made a typo on sed -- left off the filename. I couldn't ctrl-c the command, so I suspended and used kill:

This caused bash to exit. I was in screen at the time, and the index in the list of screens disappeared, processes that were backgrounded in that bash session were killed. This seems erroneous. Another distilled this significantly, and this command exibits the same behavior on ctrl-c:

DrkShadow <drkshadow>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by chet (Updated the item)
  • -unavailable- added by dualbus (Posted a comment)
  • -unavailable- added by drkshadow (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue Nov 17 21:37:55 2015chetStatusWorks For Me=>Done
    Fri Nov 13 15:29:01 2015chetStatusNone=>Works For Me

    Back to the top


    Powered by Savane 3.1-cleanup