From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Help understanding some bad emacs behavior Date: Sun, 16 Nov 2014 21:10:14 -0500 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1416190259 19940 80.91.229.3 (17 Nov 2014 02:10:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 17 Nov 2014 02:10:59 +0000 (UTC) Cc: emacs-devel@gnu.org To: Austin Bingham Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 17 03:10:53 2014 Return-path: Envelope-to: ged-emacs-devel@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 1XqBmF-0005Wc-KW for ged-emacs-devel@m.gmane.org; Mon, 17 Nov 2014 03:10:51 +0100 Original-Received: from localhost ([::1]:45805 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqBmF-0006ue-6A for ged-emacs-devel@m.gmane.org; Sun, 16 Nov 2014 21:10:51 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42972) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqBln-0006nb-3P for emacs-devel@gnu.org; Sun, 16 Nov 2014 21:10:30 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XqBlf-00086i-6o for emacs-devel@gnu.org; Sun, 16 Nov 2014 21:10:23 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:30151) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqBlf-00086e-2a for emacs-devel@gnu.org; Sun, 16 Nov 2014 21:10:15 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsUIAGA2ZVSnWBqE/2dsb2JhbABbgw6KYssMBAICgRwXAQEBAQEBfIQDAQEDAVYjBQsLNBIUGA0kiEsJ0QQBAQEHAgEfkRQHhEsFjAupDYQaH4J7AQEB X-IPAS-Result: AsUIAGA2ZVSnWBqE/2dsb2JhbABbgw6KYssMBAICgRwXAQEBAQEBfIQDAQEDAVYjBQsLNBIUGA0kiEsJ0QQBAQEHAgEfkRQHhEsFjAupDYQaH4J7AQEB X-IronPort-AV: E=Sophos;i="5.07,380,1413259200"; d="scan'208";a="97153172" Original-Received: from 167-88-26-132.cpe.teksavvy.com (HELO pastel.home) ([167.88.26.132]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Nov 2014 21:10:14 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 2EB6F4822; Sun, 16 Nov 2014 21:10:14 -0500 (EST) In-Reply-To: (Austin Bingham's message of "Sun, 16 Nov 2014 21:32:49 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:177376 Archived-At: > Sorry, good point. The emacs process maxes out one of my cores for a few > minutes. During this time emacs seems unresponsive to input, though it does > redraw on the screen. You can try M-x profiler-start RET RET before and M-x profiler-report RET afterwards, which should tell you where time was spent. > Maybe the deep-seeming stack of Ffuncall/exec_byte_code/etc. is normal, but > it was remarkable enough to me that I thought I'd mention it. Yes, it's perfectly normal. If you think of how an interpreter works, the C-level backtrace will typically look like a (deep) nesting of calls between functions called "eval" or "apply" or "call". > What's the best way to get that? Bear in mind that, as far as I can tell, > emacs isn't responding to input when I see this problem. And since I don't > really know where this is happening in elisp-land, I'm not sure where to > add instrumentation or anything like that. You can try (setq debug-on-quit t) and hitting C-g. If that doesn't work, do a "kill -USR2 " which should also drop you into the debugger. Stefan