From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg via Users list for the GNU Emacs text editor Newsgroups: gmane.emacs.help Subject: Re: Fwd: How do I go about debugging my Elisp code? Date: Sat, 15 Jan 2022 00:22:09 +0100 Message-ID: <871r19ykbi.fsf@zoho.eu> References: Reply-To: Emanuel Berg Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22756"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:1HdUPL8TvMPHkeawsAhheVRLu1I= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jan 15 00:23:45 2022 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n8Vv7-0005lk-3C for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 15 Jan 2022 00:23:45 +0100 Original-Received: from localhost ([::1]:48250 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n8Vv5-0003lq-RI for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Jan 2022 18:23:43 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:47070) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8Vtl-0003k0-Di for help-gnu-emacs@gnu.org; Fri, 14 Jan 2022 18:22:21 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]:45700) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8Vtj-0003e3-LE for help-gnu-emacs@gnu.org; Fri, 14 Jan 2022 18:22:20 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1n8Vtg-0003su-Aa for help-gnu-emacs@gnu.org; Sat, 15 Jan 2022 00:22:16 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:135301 Archived-At: Jean Louis wrote: > I join to advise by Michael from Sweden Haha :D > as to make it a proper package, use byte-compiler messages > and warnings first. > > You could use M-x emacs-lisp-byte-compile to find various > warnings and that is also for debugging purposes. > > What I often do is instrumenting the function for Edebug and > using xref package to move from function to function. > > Here is the method: > > 1. First find the function which you suspect or wish to > debug, or the one which you are invoking. > > 2. Press C-u for prefix followed by C-M-x within the > function. This will instrument the function for Edebug. > > 3. Run the function to begin the process. Once instrumenting > process begins, click "n" for next and verify various > values and how function is executed. You will find out > what is wrong. > > 4. If you see that function is calling other function where > you think that problem exists, instrument that other > function as well. > > 5. To remove instrumentation use M-x > edebug-remove-instrumentation and remove functions which > you don't want to inspect any more. ... but good outline. -- underground experts united https://dataswamp.org/~incal