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 14:53:19 -0500 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1416167625 16577 80.91.229.3 (16 Nov 2014 19:53:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 16 Nov 2014 19:53:45 +0000 (UTC) Cc: emacs-devel@gnu.org To: Austin Bingham Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 16 20:53:38 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 1Xq5tC-00027n-5j for ged-emacs-devel@m.gmane.org; Sun, 16 Nov 2014 20:53:38 +0100 Original-Received: from localhost ([::1]:44946 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xq5tB-0002rw-Pa for ged-emacs-devel@m.gmane.org; Sun, 16 Nov 2014 14:53:37 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54473) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xq5t2-0002kf-Cf for emacs-devel@gnu.org; Sun, 16 Nov 2014 14:53:35 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xq5su-0002cO-Tu for emacs-devel@gnu.org; Sun, 16 Nov 2014 14:53:28 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:16923) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xq5su-0002cK-QF for emacs-devel@gnu.org; Sun, 16 Nov 2014 14:53:20 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsUIAGA2ZVSnWBqE/2dsb2JhbABbgw6KYssMBAICgRwXAQEBAQEBfIQDAQEDAVYjBQsLNBIUGA0kiEsJ0QQBAQEBBgEBAQEekRQHhEsFjAupDYQaH4J7AQEB X-IPAS-Result: AsUIAGA2ZVSnWBqE/2dsb2JhbABbgw6KYssMBAICgRwXAQEBAQEBfIQDAQEDAVYjBQsLNBIUGA0kiEsJ0QQBAQEBBgEBAQEekRQHhEsFjAupDYQaH4J7AQEB X-IronPort-AV: E=Sophos;i="5.07,380,1413259200"; d="scan'208";a="97141964" 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 14:53:19 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 361EB7AB8; Sun, 16 Nov 2014 14:53:19 -0500 (EST) In-Reply-To: (Austin Bingham's message of "Sun, 16 Nov 2014 13:09:43 +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:177354 Archived-At: > I'm working on some code-completion related packages (company + ycmd), and > something I'm doing is triggering some pathological behavior that I could > use help on. Care to describe what is this pathological behavior you're seeing? > Under some conditions that I haven't fully characterized yet, a thread > in emacs goes off on an extended, recursive-looking adventure of > some sort. What makes you think so? > What I'm hoping is that someone on this list can look at the > attached stack info and give me some hint as to what might be going on. Better show the Elisp backtrace rather than the C backtrace. Stefan