* bug#16665: Hitting C-c C-c in *shell* causes segmentation fault @ 2014-02-06 2:57 ` Dan Jacobson 2014-02-06 17:07 ` Glenn Morris ` (2 more replies) 0 siblings, 3 replies; 8+ messages in thread From: Dan Jacobson @ 2014-02-06 2:57 UTC (permalink / raw) To: 16665 Hitting C-c C-c in *shell* causes segmentation fault. Reproducible every time. The message always starts with sh: syntax error near unexpected token `1' and ends with Process shell segmentation fault # grep nobody /etc/passwd nobody:x:65534:65534:nobody:/nonexistent:/bin/sh # su - nobody No directory, logging in with HOME=/ $ emacs -nw -f shell sh-4.3$ C-c C-c sh-4.3$ sh: syntax error near unexpected token `1' sh-4.3$ sh: $'\b\210D\020\b\035\v\b\340\313': command not found sh-4.3$ sh: $'\b\300\347': command not found ... sh-4.3$ sh: syntax error near unexpected token `(' sh-4.3$ > Process shell segmentation fault # ls -l /bin/sh lrwxrwxrwx 1 root root 4 Mar 5 2012 /bin/sh -> bash $ bash --version GNU bash, version 4.3.0(1)-rc1 (i486-pc-linux-gnu) ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#16665: Hitting C-c C-c in *shell* causes segmentation fault 2014-02-06 2:57 ` bug#16665: Hitting C-c C-c in *shell* causes segmentation fault Dan Jacobson @ 2014-02-06 17:07 ` Glenn Morris [not found] ` <87k3d7degf.fsf_-_@jidanni.org> 2014-02-06 23:11 ` Dan Jacobson 2014-02-07 3:25 ` Dan Jacobson 2 siblings, 1 reply; 8+ messages in thread From: Glenn Morris @ 2014-02-06 17:07 UTC (permalink / raw) To: Dan Jacobson; +Cc: 16665 The shell is segfaulting, therefore seems like a shell bug. ^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <87k3d7degf.fsf_-_@jidanni.org>]
* bug#16665: Hitting C-c C-c in Emacs' *shell* causes segmentation fault [not found] ` <87k3d7degf.fsf_-_@jidanni.org> @ 2014-02-07 3:16 ` Chet Ramey 0 siblings, 0 replies; 8+ messages in thread From: Chet Ramey @ 2014-02-07 3:16 UTC (permalink / raw) To: Dan Jacobson, bug-bash, rgm; +Cc: 16665, chet.ramey On 2/6/14, 6:11 PM, Dan Jacobson wrote: > Dear Bug-Bash gentlemen, > http://debbugs.gnu.org/16665 says it seems like a bash bug. > Please have a look if you are also an emacs person. OK, I'll bite. What is C-c C-c supposed to do? It looks like it just spews a bunch of garbage to your screen. Is that the intent? -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/ ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#16665: Hitting C-c C-c in Emacs' *shell* causes segmentation fault 2014-02-06 2:57 ` bug#16665: Hitting C-c C-c in *shell* causes segmentation fault Dan Jacobson 2014-02-06 17:07 ` Glenn Morris @ 2014-02-06 23:11 ` Dan Jacobson 2014-02-07 3:25 ` Dan Jacobson 2 siblings, 0 replies; 8+ messages in thread From: Dan Jacobson @ 2014-02-06 23:11 UTC (permalink / raw) To: bug-bash, rgm; +Cc: 16665 Dear Bug-Bash gentlemen, http://debbugs.gnu.org/16665 says it seems like a bash bug. Please have a look if you are also an emacs person. ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#16665: Hitting C-c C-c in Emacs' *shell* causes segmentation fault 2014-02-06 2:57 ` bug#16665: Hitting C-c C-c in *shell* causes segmentation fault Dan Jacobson 2014-02-06 17:07 ` Glenn Morris 2014-02-06 23:11 ` Dan Jacobson @ 2014-02-07 3:25 ` Dan Jacobson 2 siblings, 0 replies; 8+ messages in thread From: Dan Jacobson @ 2014-02-07 3:25 UTC (permalink / raw) To: chet.ramey; +Cc: bug-bash, 16665 >>>>> "CR" == Chet Ramey <chet.ramey@case.edu> writes: CR> OK, I'll bite. What is C-c C-c supposed to do? It looks like it just CR> spews a bunch of garbage to your screen. Is that the intent? C-c C-c runs the command comint-interrupt-subjob, which is an interactive compiled Lisp function in `comint.el'. (comint-interrupt-subjob) Interrupt the current subjob. This command also kills the pending input between the process mark and point. ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#16665: Hitting C-c C-c in Emacs' *shell* causes segmentation fault [not found] <52F45028.6030509@case.edu> 2014-02-06 2:57 ` bug#16665: Hitting C-c C-c in *shell* causes segmentation fault Dan Jacobson @ 2014-02-07 3:27 ` Chris Down 2014-02-07 3:32 ` Glenn Morris [not found] ` <878utnd2o9.fsf@jidanni.org> 3 siblings, 0 replies; 8+ messages in thread From: Chris Down @ 2014-02-07 3:27 UTC (permalink / raw) To: Chet Ramey; +Cc: Dan Jacobson, 16665, bug-bash [-- Attachment #1: Type: text/plain, Size: 589 bytes --] On 2014-02-06 22:16:56 -0500, Chet Ramey wrote: > OK, I'll bite. What is C-c C-c supposed to do? It looks like it just > spews a bunch of garbage to your screen. Is that the intent? According to the Emacs manual[0]: > Interrupt the shell or its current subjob if any > (comint-interrupt-subjob). This command also kills any shell input > pending in the shell buffer and not yet sent. I should disclaim that I'm not an Emacs user, so it's quite possible that I am looking at the wrong part of the manual. [0]: http://www.gnu.org/software/emacs/manual/html_node/emacs/Shell-Mode.html [-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* bug#16665: Hitting C-c C-c in Emacs' *shell* causes segmentation fault [not found] <52F45028.6030509@case.edu> 2014-02-06 2:57 ` bug#16665: Hitting C-c C-c in *shell* causes segmentation fault Dan Jacobson 2014-02-07 3:27 ` Chris Down @ 2014-02-07 3:32 ` Glenn Morris [not found] ` <878utnd2o9.fsf@jidanni.org> 3 siblings, 0 replies; 8+ messages in thread From: Glenn Morris @ 2014-02-07 3:32 UTC (permalink / raw) To: chet.ramey; +Cc: bug-bash, 16665 Chet Ramey wrote: > What is C-c C-c supposed to do? It pretty much just sends SIGINT. ^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <878utnd2o9.fsf@jidanni.org>]
* bug#16665: Hitting C-c C-c in Emacs' *shell* causes segmentation fault [not found] ` <878utnd2o9.fsf@jidanni.org> @ 2014-02-07 14:13 ` Chet Ramey 0 siblings, 0 replies; 8+ messages in thread From: Chet Ramey @ 2014-02-07 14:13 UTC (permalink / raw) To: Dan Jacobson; +Cc: chet.ramey, 16665, bug-bash On 2/6/14 10:25 PM, Dan Jacobson wrote: >>>>>> "CR" == Chet Ramey <chet.ramey@case.edu> writes: > > CR> OK, I'll bite. What is C-c C-c supposed to do? It looks like it just > CR> spews a bunch of garbage to your screen. Is that the intent? > > C-c C-c runs the command comint-interrupt-subjob, which is an > interactive compiled Lisp function in `comint.el'. Thanks, that was what I needed. I fixed this for bash-4.3 release. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/ ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2014-02-07 14:13 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <52F45028.6030509@case.edu> 2014-02-06 2:57 ` bug#16665: Hitting C-c C-c in *shell* causes segmentation fault Dan Jacobson 2014-02-06 17:07 ` Glenn Morris [not found] ` <87k3d7degf.fsf_-_@jidanni.org> 2014-02-07 3:16 ` bug#16665: Hitting C-c C-c in Emacs' " Chet Ramey 2014-02-06 23:11 ` Dan Jacobson 2014-02-07 3:25 ` Dan Jacobson 2014-02-07 3:27 ` Chris Down 2014-02-07 3:32 ` Glenn Morris [not found] ` <878utnd2o9.fsf@jidanni.org> 2014-02-07 14:13 ` Chet Ramey
Code repositories for project(s) associated with this external index https://git.savannah.gnu.org/cgit/emacs.git https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.