From 2da97a5afa420a85577ac355ec369bf45c2bb5ee Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 1 Oct 2009 23:27:18 +0200 Subject: open_issues/m4_vs_stack: New page. --- open_issues/m4_vs_stack.mdwn | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 open_issues/m4_vs_stack.mdwn (limited to 'open_issues') diff --git a/open_issues/m4_vs_stack.mdwn b/open_issues/m4_vs_stack.mdwn new file mode 100644 index 00000000..c92cfb00 --- /dev/null +++ b/open_issues/m4_vs_stack.mdwn @@ -0,0 +1,21 @@ +[[!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]] + + m4 (1.4.13-1+hurd.2) unreleased; urgency=low + + * Drop stack overflow (checks/stackovf) check, test-c-stack and + test-c-stack2 checks, and /dev/null/ (test-open and test-fopen) checks. + + -- Samuel Thibault Tue, 18 Aug 2009 20:54:30 +0000 + + that was a quick fix (as not having m4 makes autoconf uninstallable, which is quite a problem) + there's probably something wrong in the stack management of the Hurd, I haven't investigated -- cgit v1.2.3 From 5969e48a9f70aa37d89c5665bd22fce16af92ab3 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sat, 3 Oct 2009 15:52:25 +0200 Subject: open_issues/bash_vs_screen_vs_sigint: New page. --- open_issues/bash_vs_screen_vs_sigint.mdwn | 68 +++++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 open_issues/bash_vs_screen_vs_sigint.mdwn (limited to 'open_issues') diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn new file mode 100644 index 00000000..e6d9b41c --- /dev/null +++ b/open_issues/bash_vs_screen_vs_sigint.mdwn @@ -0,0 +1,68 @@ +[[!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 + error in the not-*screen* case, and in the **128** value for `$?`. The + former is an error, and the latter may be as expected. (Check GNU/Linux + with that *bash* version.) + + * 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 + * 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. + + +To sum up: + + * *bash*: 4.0 packages have the MIG error, and the 128 return value difference. + + * *screen*: new package doesn't react to `C-c` anymore. -- cgit v1.2.3 From 9a04763a922a8f5084035d44eadd35709958fedc Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sat, 3 Oct 2009 16:03:53 +0200 Subject: open_issues/bash_vs_screen_vs_sigint: Another version of glibc. --- open_issues/bash_vs_screen_vs_sigint.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'open_issues') diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn index e6d9b41c..8260b004 100644 --- a/open_issues/bash_vs_screen_vs_sigint.mdwn +++ b/open_issues/bash_vs_screen_vs_sigint.mdwn @@ -40,7 +40,7 @@ this: former is an error, and the latter may be as expected. (Check GNU/Linux with that *bash* version.) - * 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 + * 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. -- cgit v1.2.3 From 78188ccfd77b9d5c6a0e95232536cdabc616bd85 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sat, 3 Oct 2009 16:08:37 +0200 Subject: open_issues/bash_vs_screen_vs_sigint: Improve. --- open_issues/bash_vs_screen_vs_sigint.mdwn | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'open_issues') diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn index 8260b004..c8a31a15 100644 --- a/open_issues/bash_vs_screen_vs_sigint.mdwn +++ b/open_issues/bash_vs_screen_vs_sigint.mdwn @@ -35,7 +35,7 @@ this: * 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 + This differs from the behavior of the earlier *bash* version in the MIG reply error in the not-*screen* case, and in the **128** value for `$?`. The former is an error, and the latter may be as expected. (Check GNU/Linux with that *bash* version.) @@ -63,6 +63,6 @@ this: To sum up: - * *bash*: 4.0 packages have the MIG error, and the 128 return value difference. - - * *screen*: new package doesn't react to `C-c` anymore. + * *bash*: 4.0 packages print `^C` at the shell prompt, have the MIG reply + error, and the difference in the value 128 for `$?`. + * *screen*: new package causes that invokee doesn't react to `C-c` anymore. -- cgit v1.2.3 From 7074ada224a2033f84f87d343378e84b7ae7771a Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 5 Oct 2009 23:12:20 +0200 Subject: open_issues/xen_crash_copy-size_le_page_size: Tag as open_issue_xen. --- open_issues/xen_crash_copy-size_le_page_size.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'open_issues') diff --git a/open_issues/xen_crash_copy-size_le_page_size.mdwn b/open_issues/xen_crash_copy-size_le_page_size.mdwn index 0aa030fd..f2d8081e 100644 --- a/open_issues/xen_crash_copy-size_le_page_size.mdwn +++ b/open_issues/xen_crash_copy-size_le_page_size.mdwn @@ -8,7 +8,7 @@ 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_gnumach]] +[[!tag open_issue_xen]] `/dev/hd2` is 2 GiB in size (backed by LVM), unformatted. -- cgit v1.2.3 From 46026d07791386c61acbdd26db4b5a77e92356bb Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Tue, 6 Oct 2009 23:37:48 +0200 Subject: open_issues/screen: New page. --- open_issues/screen.mdwn | 106 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 open_issues/screen.mdwn (limited to 'open_issues') diff --git a/open_issues/screen.mdwn b/open_issues/screen.mdwn new file mode 100644 index 00000000..cc2110ad --- /dev/null +++ b/open_issues/screen.mdwn @@ -0,0 +1,106 @@ +[[!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]] + +Revisit this issue: [[!debbug 97343]] -- special handling of `TIOCSCTTY` +depending on `__GNU__`. + +--- + +`#ifdef linux` and friends are used in quite a number of places. + +--- + +All diffs are GNU/Linux vs. GNU/Hurd. + + /* + * If your system supports BSD4.4's seteuid() and setegid(), define + * HAVE_SETEUID. + */ + -/* #undef HAVE_SETEUID */ + +#define HAVE_SETEUID 1 + +TODO: check. + +--- + + /* + * define HAVE_SVR4_PTYS if you have a /dev/ptmx character special + * device and support the ptsname(), grantpt(), unlockpt() functions. + */ + -#define HAVE_SVR4_PTYS 1 + +/* #undef HAVE_SVR4_PTYS */ + + /* + * define HAVE_GETPT if you have the getpt() function. + */ + #define HAVE_GETPT 1 + + /* + * define HAVE_OPENPTY if your system has the openpty() call. + */ + -/* #undef HAVE_OPENPTY */ + +#define HAVE_OPENPTY 1 + + /* + * define PTYRANGE0 and or PTYRANGE1 if you want to adapt screen + * to unusual environments. E.g. For SunOs the defaults are "qpr" and + * "0123456789abcdef". For SunOs 4.1.2 + * #define PTYRANGE0 "pqrstuvwxyzPQRST" + * is recommended by Dan Jacobson. + */ + -/* #undef PTYRANGE0 */ + -/* #undef PTYRANGE1 */ + +#define PTYRANGE0 "pq" + +#define PTYRANGE1 "0123456789abcdefghijklmnopqrstuv" + +TODO: check: `HAVE_SVR4_PTYS` is due to `configure.in` doing `test -c +/dev/ptmx`. But: even if we don't have that file, we still have `ptsname`, +`grantpt`, `unlockpt`. + +--- + + gcc -c -I. -I. -g -O2 -O2 -g -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers pty.c + +pty.c: In function 'OpenPTY': + +pty.c:323: warning: implicit declaration of function 'openpty' + +pty.c: At top level: + +pty.c:75: warning: 'PtyName' defined but not used + +pty.c:86: warning: 'PtyProto' defined but not used + +pty.c:87: warning: 'TtyProto' defined but not used + +TODO: check. + +--- + + --- linux/osdef.h 2009-10-06 18:43:53.000000000 +0200 + +++ screen-4.0.3/osdef.h 2009-10-06 18:49:49.000000000 +0200 + @@ -42,13 +42,19 @@ + #endif + + #ifdef SYSV + +extern char *strchr __P((char *, int)); + +extern char *strrchr __P((char *, int)); + +extern char *memset __P((char *, int, int)); + +extern int memcmp __P((char *, char *, int)); + #else + #endif + + #ifndef USEBCOPY + # ifdef USEMEMCPY + +extern void memcpy __P((char *, char *, int)); + # else + # ifdef USEMEMMOVE + +extern void memmove __P((char *, char *, int)); + # else + # endif + # endif + +TODO: check. -- cgit v1.2.3 From dff5f1a813f641100cc16b520e64502fae567f4f Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 7 Oct 2009 22:01:04 +0200 Subject: open_issues/bash_vs_screen_vs_sigint: The screen issue is resolved: Debian bug #522689#38. --- open_issues/bash_vs_screen_vs_sigint.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'open_issues') diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn index c8a31a15..8dbb6816 100644 --- a/open_issues/bash_vs_screen_vs_sigint.mdwn +++ b/open_issues/bash_vs_screen_vs_sigint.mdwn @@ -58,11 +58,11 @@ this: * shell prompt: **no reaction (nothing printed)**; `$?` thus is **unchanged**. * `sleep 10` running: **`^C` printed**, SIGINT is **not** sent. - The *screen* behavior differs. + The *screen* behavior differs -- [[!debbug 522689#38]]. To sum up: * *bash*: 4.0 packages print `^C` at the shell prompt, have the MIG reply error, and the difference in the value 128 for `$?`. - * *screen*: new package causes that invokee doesn't react to `C-c` anymore. + * *screen*: new package causes that invokee doesn't react to `C-c` anymore. -- cgit v1.2.3 From fc2488eb1ebe33ecd88880138fc640e4aafcb3cb Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 7 Oct 2009 22:15:31 +0200 Subject: open_issues/bash_vs_screen_vs_sigint: A few bash issues are the same on GNU/Linux. --- open_issues/bash_vs_screen_vs_sigint.mdwn | 23 +++++++++++------------ 1 file changed, 11 insertions(+), 12 deletions(-) (limited to 'open_issues') diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn index 8dbb6816..371b622e 100644 --- a/open_issues/bash_vs_screen_vs_sigint.mdwn +++ b/open_issues/bash_vs_screen_vs_sigint.mdwn @@ -29,30 +29,30 @@ this: * 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. + * 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. + * 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, and in the **128** value for `$?`. The - former is an error, and the latter may be as expected. (Check GNU/Linux - with that *bash* version.) + error in the not-*screen* case, and, when in command-line editing mode, the + displaying of `^C` (same on GNU/Linux), and the 128 value for `$?` (same on + GNU/Linux). * 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**. + * 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**. + * 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**. + * 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**. @@ -63,6 +63,5 @@ this: To sum up: - * *bash*: 4.0 packages print `^C` at the shell prompt, have the MIG reply - error, and the difference in the value 128 for `$?`. + * *bash*: 4.0 packages have the MIG reply error. * *screen*: new package causes that invokee doesn't react to `C-c` anymore. -- cgit v1.2.3 From a6088679c4b7a8b8dec469aeaf7f422fea44b455 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 7 Oct 2009 22:21:51 +0200 Subject: open_issues/gdb_gcore: New page. --- open_issues/gdb_gcore.mdwn | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 open_issues/gdb_gcore.mdwn (limited to 'open_issues') diff --git a/open_issues/gdb_gcore.mdwn b/open_issues/gdb_gcore.mdwn new file mode 100644 index 00000000..7d4980f1 --- /dev/null +++ b/open_issues/gdb_gcore.mdwn @@ -0,0 +1,23 @@ +[[!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]]."]]"""]] + +[[!meta title="GDB: gcore"]] + +[[!tag open_issue_gdb]] + +GDB's `gcore` command doesn't work / needs to be implemented / ported in GDB: + + tschwinge@flubber:~ $ gcore 8371 + [New Thread 8371.1] + [New Thread 8371.2] + [New Thread 8371.3] + /media/data/home/tschwinge/core.cA0ICY:2: Error in sourced command file: + Undefined command: "gcore". Try "help". + gcore: failed to create core.8371 -- cgit v1.2.3 From 771bd0745a4d7eb990ce8d42f8ae7b4f163c4dfb Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 8 Oct 2009 08:32:20 +0200 Subject: open_issues/bash_vs_screen_vs_sigint: bash 4.0 error, fixed for 4.1. --- open_issues/bash_vs_screen_vs_sigint.mdwn | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'open_issues') diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn index 371b622e..f5ce5166 100644 --- a/open_issues/bash_vs_screen_vs_sigint.mdwn +++ b/open_issues/bash_vs_screen_vs_sigint.mdwn @@ -36,9 +36,11 @@ this: * `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, and, when in command-line editing mode, the - displaying of `^C` (same on GNU/Linux), and the 128 value for `$?` (same on - GNU/Linux). + 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: + . * 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 -- cgit v1.2.3 From 924e9702036d8a1506cc6bb07facb18e23494519 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 8 Oct 2009 09:26:42 +0200 Subject: open_issues/bash_vs_screen_vs_sigint: MIG reply error isolated to PROMPT_COMMAND being set. --- open_issues/bash_vs_screen_vs_sigint.mdwn | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) (limited to 'open_issues') diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn index f5ce5166..47d79c65 100644 --- a/open_issues/bash_vs_screen_vs_sigint.mdwn +++ b/open_issues/bash_vs_screen_vs_sigint.mdwn @@ -65,5 +65,24 @@ this: To sum up: - * *bash*: 4.0 packages have the MIG reply error. * *screen*: new package causes that invokee doesn't react to `C-c` anymore. + + * *bash*: 4.0 packages have the MIG reply error. + + After having noticed that this error doesn't occur if starting *bash* with + `--norc`, I isolated it to the following command in `.bashrc`: + + case $TERM in + xterm* | rxvt*) + PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}:${PWD}\007"';; + esac + + ... and indeed: + + tschwinge@flubber:~ $ echo "$TERM" -- "$PROMPT_COMMAND" + xterm -- echo -ne "\033]0;${USER}@${HOSTNAME}:${PWD}\007" + tschwinge@flubber:~ $ ^C + -bash: echo: write error: (ipc/mig) wrong reply message ID + tschwinge@flubber:~ $ PROMPT_COMMAND= + tschwinge@flubber:~ $ ^C + tschwinge@flubber:~ $ -- cgit v1.2.3 From f006d45dda72605da09322dc7941f2ed5629395b Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Thu, 8 Oct 2009 14:50:56 +0200 Subject: open_issues/bash_vs_screen_vs_sigint: Separate bash and screen issue. open_issues/bash: Add more information w.r.t. PROMPT_COMMAND. --- open_issues/bash.mdwn | 47 ++++++++++++++++++ open_issues/bash_vs_screen_vs_sigint.mdwn | 80 +------------------------------ open_issues/screen.mdwn | 10 ++++ 3 files changed, 59 insertions(+), 78 deletions(-) create mode 100644 open_issues/bash.mdwn (limited to 'open_issues') diff --git a/open_issues/bash.mdwn b/open_issues/bash.mdwn new file mode 100644 index 00000000..47598071 --- /dev/null +++ b/open_issues/bash.mdwn @@ -0,0 +1,47 @@ +[[!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]] + +# *bash* 4.0 vs. typing `C-c` (*SIGINT*) + +Will show `-bash: echo: write error: (ipc/mig) wrong reply message ID` unter +certain conditions. + +After having noticed that this error doesn't occur if starting *bash* with +`--norc`, I isolated it to the following command in `.bashrc`: + + case $TERM in + xterm* | rxvt*) + PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}:${PWD}\007"';; + esac + +... and indeed: + + tschwinge@flubber:~ $ echo "$TERM" -- "$PROMPT_COMMAND" + xterm -- echo -ne "\033]0;${USER}@${HOSTNAME}:${PWD}\007" + tschwinge@flubber:~ $ ^C + -bash: echo: write error: (ipc/mig) wrong reply message ID + tschwinge@flubber:~ $ PROMPT_COMMAND= + tschwinge@flubber:~ $ ^C + tschwinge@flubber:~ $ + + bash-4.0$ PROMPT_COMMAND='echo >&2 -n foo\ ' + foo bash-4.0$ ^C + + bash-4.0$ PROMPT_COMMAND='echo >&1 -n foo\ ' + foo bash-4.0$ ^C + bash: echo: write error: (ipc/mig) wrong reply message ID + + bash-4.0$ PROMPT_COMMAND='/bin/echo >&1 -n foo\ ' + foo bash-4.0$ ^C + bash: start_pipeline: pgrp pipe: (ipc/mig) wrong reply message ID + +So, there's something different with stdout in / after the SIGINT handler. diff --git a/open_issues/bash_vs_screen_vs_sigint.mdwn b/open_issues/bash_vs_screen_vs_sigint.mdwn index 47d79c65..9672041c 100644 --- a/open_issues/bash_vs_screen_vs_sigint.mdwn +++ b/open_issues/bash_vs_screen_vs_sigint.mdwn @@ -8,81 +8,5 @@ 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: - . - - * 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: - - * *screen*: new package causes that invokee doesn't react to `C-c` anymore. - - * *bash*: 4.0 packages have the MIG reply error. - - After having noticed that this error doesn't occur if starting *bash* with - `--norc`, I isolated it to the following command in `.bashrc`: - - case $TERM in - xterm* | rxvt*) - PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}:${PWD}\007"';; - esac - - ... and indeed: - - tschwinge@flubber:~ $ echo "$TERM" -- "$PROMPT_COMMAND" - xterm -- echo -ne "\033]0;${USER}@${HOSTNAME}:${PWD}\007" - tschwinge@flubber:~ $ ^C - -bash: echo: write error: (ipc/mig) wrong reply message ID - tschwinge@flubber:~ $ PROMPT_COMMAND= - tschwinge@flubber:~ $ ^C - tschwinge@flubber:~ $ + * [[bash]] + * [[screen]] diff --git a/open_issues/screen.mdwn b/open_issues/screen.mdwn index cc2110ad..6ece5c40 100644 --- a/open_issues/screen.mdwn +++ b/open_issues/screen.mdwn @@ -10,6 +10,16 @@ License|/fdl]]."]]"""]] [[!tag open_issue_porting]] +Typing `C-c` (*SIGINT*) in a *screen* session (Debian package 4.0.3-14; -11 is +fine): + + * shell prompt: no reaction (nothing printed) + * `sleep 10` running: `^C` printed, but SIGINT is not sent. + +[[!debbug 522689#38]]. + +--- + Revisit this issue: [[!debbug 97343]] -- special handling of `TIOCSCTTY` depending on `__GNU__`. -- cgit v1.2.3