From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: get backtrace of handle-switch-frame Date: Mon, 25 Mar 2019 08:24:24 -0400 Message-ID: References: <87tvfs2kwj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="113351"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Mar 25 13:24:56 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h8Oeu-000TNl-0o for geh-help-gnu-emacs@m.gmane.org; Mon, 25 Mar 2019 13:24:56 +0100 Original-Received: from localhost ([127.0.0.1]:41845 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8Oet-00024p-0k for geh-help-gnu-emacs@m.gmane.org; Mon, 25 Mar 2019 08:24:55 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:47674) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8OeW-00023V-GM for help-gnu-emacs@gnu.org; Mon, 25 Mar 2019 08:24:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h8OeV-0004GN-Jx for help-gnu-emacs@gnu.org; Mon, 25 Mar 2019 08:24:32 -0400 Original-Received: from [195.159.176.226] (port=44424 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h8OeV-0004F7-B7 for help-gnu-emacs@gnu.org; Mon, 25 Mar 2019 08:24:31 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1h8OeT-000Srm-CA for help-gnu-emacs@gnu.org; Mon, 25 Mar 2019 13:24:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:2Kz4hmJSrrN3NgPbiHhXFq/dvN4= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:119735 Archived-At: > Hello, is it possble to get the backtrace of function `handle-switch-frame` > so that I can find out the cause of an unexpected frame switch event? I'm not completely sure what you mean by "the backtrace of function <...>", but I assume you want to get the backtrace at the point where the function is called. `M-x debug-on-entry RET handle-switch-frame RET` should do just that. But I think you'll be very disappointed with the result: this is a function bound to an event, and these are decoupled from the code that generates/triggers the event by a buffer (this is the buffer that's used to remember the keys you pressed while a long-running command is still ongoing). So the backtrace will likely tell you very little and specifically it will not tell you the cause of the unexpected frame switch event. Stefan