From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stephen Berman Newsgroups: gmane.emacs.devel Subject: Re: misbehavior in shell window with ksh Date: Tue, 02 May 2017 14:35:44 +0200 Message-ID: <87efw7jv1b.fsf@rosalinde> 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> <83h913iq9x.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1493728566 25450 195.159.176.226 (2 May 2017 12:36:06 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 2 May 2017 12:36:06 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) Cc: emacs-devel@gnu.org, mkupfer@alum.berkeley.edu To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 02 14:36:02 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 1d5X2A-0006Rf-Dm for ged-emacs-devel@m.gmane.org; Tue, 02 May 2017 14:36:02 +0200 Original-Received: from localhost ([::1]:58658 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5X2B-0001eK-HY for ged-emacs-devel@m.gmane.org; Tue, 02 May 2017 08:36:03 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37869) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5X23-0001eE-In for emacs-devel@gnu.org; Tue, 02 May 2017 08:35:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d5X22-00056o-IA for emacs-devel@gnu.org; Tue, 02 May 2017 08:35:55 -0400 Original-Received: from mout.gmx.net ([212.227.15.15]:59279) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d5X1y-00054R-GD; Tue, 02 May 2017 08:35:50 -0400 Original-Received: from rosalinde ([83.135.28.111]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MDhba-1dI7Po0Mn8-00H5HY; Tue, 02 May 2017 14:35:46 +0200 In-Reply-To: <83h913iq9x.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 02 May 2017 12:03:54 +0300") X-Provags-ID: V03:K0:HSYTfzdJnGUUqh+jNVw1/G1wKcmtP7iJui2lC+V8eruDYHh6HwG 3kYiFaYzDZLWJ3hCzx+Yjn2Be7dgNUlmxzrwMX08vBcrtO0Yz2ryFg6DDSwN3JgpYZQqlzV 4X+RNOHrjvZXuf4vbdracOJ7LEZWi/AQHCuMjUBAhLamBzdpSGEUeB6elUePWGoDr6KFs44 cCqhB7MGi1sqoN+hvjifg== X-UI-Out-Filterresults: notjunk:1;V01:K0:uBidVCG1zWc=:GSwixuN6XALP9YoELdNsOl 3tumAbn/qGaIfL2Q2g52U8pPd9emEW1iqu6rHc71MiDl7C4q9piZ2ZdmTVTHA9g/u2/q5+s+C Kecpg832noQJI1nIFaWZdGwLQQjA+nG7bnoIg6/p/A321h58N+pWfFRB4gQVc7iWw66OGvQb7 vPJtyTN4TsykN3zOmbfs33oTAR7OidU1QdVNf2GRMB70gB/3zo9bDHKFnSTbIgZMmahxfmo5i Hv4ds1mRuJRRC2VVI5SP9ZVWHdC7l+jg+7Qp5v4rn3XOl7QzPKdnYgFVHLE2hxEqPoNeZKqdw 8x7G0AeYT+XVlYc8gjaDlCOhKw1UFxoU4eIndz90684YnkFcBc9BW6DpXp0GaZGHmLieORHal DP2qZfjHGt+OgjBm+agV92AcWMVWgOBfT2SIvOI7Ht+a4ih03ByaP6/SaTEQI9SBfifV4bGBD Rpn7vjJSD18M4vf8JaySKXFLjKp7OvZOmWBlveXX2jhXlPM3yXwt5uZEXT2/6gprkg2DGm4Zw L6m+dlj+/Iv5hydspOI2A4xzhr5PeT1ZEi9yYyqbO06QgCvC+UiWgwmOICDdfVdZXEaWI9Efr XZdbOMjay4NRQNbv+x/hA7fTHWg4MV6cXsQHCiNfncSdEPHWKV2yTZByPyBojMxSlxxXfwBUV ywl+avGnHq8sETh9GRfCMYndV1axVGby/1aU5mgj/3smRfFpuds9mhaq2MkCl1M5gzNbpb4XJ 1wcDq2ezwhqBVVEJOyEsYIJaQZFB06G56iPLBiPH1XtruzCRNNUaNYH2c4fjN2bcr+Vegq9M X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 212.227.15.15 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:214513 Archived-At: On Tue, 02 May 2017 12:03:54 +0300 Eli Zaretskii wrote: >> 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? Unfortunately not. FTR: I instrumented comint-output-filter for Edebug and started the recipe. On entering `ksh RET' at the shell prompt, Edebug took control and I typed `d' and got this backtrace: comint-output-filter(# "steve@rosalinde:/home/steve> ") I typed `q' and continued with the recipe, and at `C-x 0' (M-o and M-0 above were typos) Edebug again took over, and `d' produced this backtrace: 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. If you can advise me what to try in gdb, I can do that. I did try setting a breakpoint at Fprocess_filter but subsequently typing `C-x 0' did not stop execution (but did result in "> " getting inserted). Steve Berman