From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#20074: edebug tracing can't be stopped with 'S' Date: Fri, 13 Mar 2015 13:07:14 +0200 Message-ID: <83r3st2m1p.fsf@gnu.org> References: <83wq2n4i4f.fsf@gnu.org> <87fv999p2q.fsf@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1426245233 9076 80.91.229.3 (13 Mar 2015 11:13:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Mar 2015 11:13:53 +0000 (UTC) Cc: 20074@debbugs.gnu.org To: Alexis Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Mar 13 12:13:41 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YWNXB-0000Ep-5j for geb-bug-gnu-emacs@m.gmane.org; Fri, 13 Mar 2015 12:13:41 +0100 Original-Received: from localhost ([::1]:36253 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YWNXA-0001Qu-GB for geb-bug-gnu-emacs@m.gmane.org; Fri, 13 Mar 2015 07:13:40 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41305) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YWNV9-0006Lo-6k for bug-gnu-emacs@gnu.org; Fri, 13 Mar 2015 07:11:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YWNRi-0007yg-QU for bug-gnu-emacs@gnu.org; Fri, 13 Mar 2015 07:08:06 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:46030) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YWNRi-0007yc-N9 for bug-gnu-emacs@gnu.org; Fri, 13 Mar 2015 07:08:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YWNRi-00006E-Fc for bug-gnu-emacs@gnu.org; Fri, 13 Mar 2015 07:08:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 13 Mar 2015 11:08:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20074 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 20074-submit@debbugs.gnu.org id=B20074.1426244845331 (code B ref 20074); Fri, 13 Mar 2015 11:08:02 +0000 Original-Received: (at 20074) by debbugs.gnu.org; 13 Mar 2015 11:07:25 +0000 Original-Received: from localhost ([127.0.0.1]:44598 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YWNR6-00005H-LE for submit@debbugs.gnu.org; Fri, 13 Mar 2015 07:07:24 -0400 Original-Received: from mtaout24.012.net.il ([80.179.55.180]:55103) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YWNR4-000053-RW for 20074@debbugs.gnu.org; Fri, 13 Mar 2015 07:07:23 -0400 Original-Received: from conversion-daemon.mtaout24.012.net.il by mtaout24.012.net.il (HyperSendmail v2007.08) id <0NL500I00D6JT900@mtaout24.012.net.il> for 20074@debbugs.gnu.org; Fri, 13 Mar 2015 12:59:27 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout24.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NL5007NSD73YA90@mtaout24.012.net.il>; Fri, 13 Mar 2015 12:59:27 +0200 (IST) In-reply-to: <87fv999p2q.fsf@gmail.com> X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:100437 Archived-At: > From: Alexis > Date: Fri, 13 Mar 2015 21:19:57 +1100 > > i'd be interested to know whether this behaviour is considered a > bug. Yes, it's a bug (or maybe a long-missing feature: I'm not sure it has ever worked as intended). > When i see tight code loops like this, my first thought - > based on > experience - is: "When is the rest of the system [in this > instance, the Emacs system] going to get a chance to do anything, > such as read and handle input events?" > > Do Emacs devs feel that Emacs should still be reasonably > responsive in the face of such tight loops? Where do you see a tight loop during Edebug tracing?