summaryrefslogtreecommitdiff
path: root/open_issues/bash_vs_screen_vs_sigint.mdwn
blob: f5ce5166f688349e03531ab5c9e8821ce5d81f83 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]]

[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]

[[!tag open_issue_porting]]

Typing `C-c` (*SIGINT*), different versions of *bash* and *screen* respond like
this:

  * GNU/Linux; Ubuntu package 3.2-5 / `$BASH_VERSION` is `3.2.48(1)-release`
      * plain
          * shell prompt: new line / prompt printed; `$?` is 1.
          * `sleep 10` running: `^C` printed; SIGINT is sent; `$?` is 130.
      * in a *screen* session (Ubuntu package 4.0.3-11ubuntu4): exactly the same.

  * GNU/Hurd; Debian package 3.2-6+b1 (equals 3.2-6) / `$BASH_VERSION` is `3.2.48(1)-release`; *libc0.3* Debian package 2.9-25
      * plain
          * shell prompt: new line / prompt printed; `$?` is 1.
          * `sleep 10` running: `^C` printed; SIGINT is sent; `$?` is 130.
      * in a *screen* session (Debian package 4.0.3-11): exactly the same.
    
    This is equivalent to the GNU/Linux behavior.

  * GNU/Hurd; Debian package 4.0-4 / `$BASH_VERSION` is `4.0.28(1)-release`; *libc0.3* Debian package 2.9-25
      * plain
          * shell prompt: `^C`, then new line, then **`-bash: echo: write error: (ipc/mig) wrong reply message ID`**, then new line / prompt printed; `$?` is 128.
          * `sleep 10` running: `^C` printed, SIGINT is sent; `$?` is 130.
      * in a *screen* session (Debian package 4.0.3-11)
          * shell prompt: `^C`, then new line / prompt printed; `$?` is 128.
          * `sleep 10` running: `^C` printed; SIGINT is sent; `$?` is 130.
    
    This differs from the behavior of the earlier *bash* version in the MIG reply
    error in the not-*screen* case.  The difference in command-line editing
    mode, the displaying of `^C` (same on GNU/Linux), and / or the value 128
    for `$?` (same on GNU/Linux) is a bash 4.0 regression that has been fixed
    for 4.1 already:
    <http://lists.gnu.org/archive/html/bug-bash/2009-10/msg00040.html>.

  * GNU/Hurd; Debian package 4.0-7 / `$BASH_VERSION` is `4.0.33(1)-release`; *libc0.3* Debian packages 2.9-19, 2.9-25, 2.9-27
      * plain
          * shell prompt: `^C`, then new line, then **`-bash: echo: write error: (ipc/mig) wrong reply message ID`**, then new line / prompt printed; `$?` is 128.
          * `sleep 10` running: `^C` printed; SIGINT is sent; `$?` is 130.
      * in a *screen* session (Debian package 4.0.3-11)
          * shell prompt: `^C`, then new line / prompt printed; `$?` is 128.
          * `sleep 10` running: `^C` printed; SIGINT is sent; `$?` is 130.
    
    This is equivalent to the *bash* 4.0-4 / 4.0.28(1) behavior.

  * GNU/Hurd; Debian package 4.0-7 / `$BASH_VERSION` is `4.0.33(1)-release`; *libc0.3* Debian package 2.9-27
      * plain
          * shell prompt: `^C`, then new line, then **`-bash: echo: write error: (ipc/mig) wrong reply message ID`**, then new line / prompt printed; `$?` is 128.
          * `sleep 10` running: `^C` printed; SIGINT is sent; `$?` is 130.
      * in a *screen* session (Debian package 4.0.3-14)
          * shell prompt: **no reaction (nothing printed)**; `$?` thus is **unchanged**.
          * `sleep 10` running: **`^C` printed**, SIGINT is **not** sent.
    
    The *screen* behavior differs -- [[!debbug 522689#38]].


To sum up:

  * *bash*: 4.0 packages have the MIG reply error.
  * <strike>*screen*: new package causes that invokee doesn't react to `C-c` anymore.</strike>