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 19:32:31 +0300 Message-ID: <83fugni5i8.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> <83h913iq9x.fsf@gnu.org> <87efw7jv1b.fsf@rosalinde> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1493742845 3396 195.159.176.226 (2 May 2017 16:34:05 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 2 May 2017 16:34:05 +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 18:34:01 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 1d5akS-0000nR-WD for ged-emacs-devel@m.gmane.org; Tue, 02 May 2017 18:34:01 +0200 Original-Received: from localhost ([::1]:60073 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5akY-0001p3-Dt for ged-emacs-devel@m.gmane.org; Tue, 02 May 2017 12:34:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58871) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5ajW-0001eW-2z for emacs-devel@gnu.org; Tue, 02 May 2017 12:33:02 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d5ajS-0004aB-Ud for emacs-devel@gnu.org; Tue, 02 May 2017 12:33:02 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:32834) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d5ajS-0004a0-Qy; Tue, 02 May 2017 12:32:58 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2985 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1d5ajR-0007PS-Ki; Tue, 02 May 2017 12:32:58 -0400 In-reply-to: <87efw7jv1b.fsf@rosalinde> (message from Stephen Berman on Tue, 02 May 2017 14:35:44 +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:214520 Archived-At: > From: Stephen Berman > Cc: mkupfer@alum.berkeley.edu, emacs-devel@gnu.org > Date: Tue, 02 May 2017 14:35:44 +0200 > > > 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. Get Emacs to stop in comint-output-filter using Edebug, then attach GDB, make sure src/.gdbinit is being source'd by GDB, and type (gdb) bt This should producve both C-level backtrace and Lisp-level backtrace.