From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: misbehavior in shell window with ksh Date: Tue, 02 May 2017 12:03:54 +0300 Message-ID: <83h913iq9x.fsf@gnu.org> References: <12812.1493593946@alto> <83o9vdjcl6.fsf@gnu.org> <87pofszvue.fsf@rosalinde> <837f20ke4g.fsf@gnu.org> <87inlkzlkt.fsf@rosalinde> <831ss8k40f.fsf@gnu.org> <87bmrczi9s.fsf@rosalinde> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1493715909 32659 195.159.176.226 (2 May 2017 09:05:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 2 May 2017 09:05:09 +0000 (UTC) Cc: emacs-devel@gnu.org, mkupfer@alum.berkeley.edu To: Stephen Berman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 02 11:05:00 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d5Tjw-0008Ib-ML for ged-emacs-devel@m.gmane.org; Tue, 02 May 2017 11:05:00 +0200 Original-Received: from localhost ([::1]:57596 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5Tjz-0003WL-18 for ged-emacs-devel@m.gmane.org; Tue, 02 May 2017 05:05:03 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33505) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5TjN-0003W3-Ms for emacs-devel@gnu.org; Tue, 02 May 2017 05:04:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d5TjI-0005is-28 for emacs-devel@gnu.org; Tue, 02 May 2017 05:04:25 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:55199) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5TjH-0005il-Vl; Tue, 02 May 2017 05:04:20 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2360 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1d5TjH-0003Cy-9u; Tue, 02 May 2017 05:04:19 -0400 In-reply-to: <87bmrczi9s.fsf@rosalinde> (message from Stephen Berman on Mon, 01 May 2017 17:52:31 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:214511 Archived-At: > From: Stephen Berman > Cc: mkupfer@alum.berkeley.edu, emacs-devel@gnu.org > Date: Mon, 01 May 2017 17:52:31 +0200 > > > Can you show the backtrace for the invocation of comint-output-filter? > > After `M-o' in the recipe I did `M-: (debug-on-entry > 'comint-output-filter) RET' (when I tried `M-x debug-on-entry RET' the string > "> " was then inserted into the *shell* buffer). This showed this backtrace: > > Debugger entered--entering a function: > * comint-output-filter(# "> ") > > I typed `q' then proceeded with `M-0' from the recipe, which produced > the same backtrace. Why isn't the caller of comint-output-filter shown? What if you step into comint-output-filter with Edebug (as you already seem to have a way of doing that), then type 'd' to produce a backtrace? Does that show who called comint-output-filter? It could be that it is called by the process-filter mechanism, which is in C. But what we want to know is where does the 2nd arg of comint-output-filter comes from, and why. Thanks.