From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pankaj Jangid Newsgroups: gmane.emacs.devel Subject: Re: Hunting the culprit package Date: Wed, 31 Aug 2022 22:50:01 +0530 Message-ID: <877d2ocou6.fsf@codeisgreat.org> References: <87zgflc6m9.fsf@codeisgreat.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25289"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:7yISYc69b8RsDlcllDuZ2sAPLrA= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 31 19:21:04 2022 Return-path: Envelope-to: ged-emacs-devel@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 1oTROi-0006KO-DH for ged-emacs-devel@m.gmane-mx.org; Wed, 31 Aug 2022 19:21:04 +0200 Original-Received: from localhost ([::1]:60078 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oTROg-0002Wn-MZ for ged-emacs-devel@m.gmane-mx.org; Wed, 31 Aug 2022 13:21:02 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49136) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTRNu-0001qZ-3R for emacs-devel@gnu.org; Wed, 31 Aug 2022 13:20:14 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:56312) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTRNs-0002U8-JQ for emacs-devel@gnu.org; Wed, 31 Aug 2022 13:20:13 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1oTRNq-00057S-EV for emacs-devel@gnu.org; Wed, 31 Aug 2022 19:20:10 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@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.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:294448 Archived-At: Stefan Monnier writes: > In my experience, the problem in such circumstances is most of the time > a file that was miscompiled for some reason. > Probably something like this happened. > NOTE: I said "may be", because I don't know whether it's the case > or not. On `elpa.(non)gnu.org` tarballs are not *re*built, so for > (Non)GNU ELPA packages this should never happen. Makes sense. >> Also, if this is not the correct way to approach then how to find which >> the old package that was creating the issue. > > Do the usual debugging from the details of issue itself, walking our way > back to its source? I noted this first in magit; so I reported there as well. I was informed that uninstalling "compat" and "magit" and then reinstalling "magit" and then restarting Emacs could solve the issue. This did the trick. Because magit is hooked into so many places, every part of Emacs was giving some error. For example, pressing RET on an info node was also not working. An external package can cause so much damage. Can this be prevented?