From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: How does one find out what file a library has been loaded from? Date: Tue, 19 Jul 2022 15:32:40 +0000 Message-ID: References: <83bktlnuog.fsf@gnu.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="4515"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jul 19 17:39:32 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 1oDpJs-0000wL-S4 for ged-emacs-devel@m.gmane-mx.org; Tue, 19 Jul 2022 17:39:32 +0200 Original-Received: from localhost ([::1]:60210 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oDpJq-0004fw-CI for ged-emacs-devel@m.gmane-mx.org; Tue, 19 Jul 2022 11:39:30 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46658) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oDpGk-0000kQ-Kv for emacs-devel@gnu.org; Tue, 19 Jul 2022 11:36:18 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:59358) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oDpGY-0003k0-UI; Tue, 19 Jul 2022 11:36:18 -0400 Original-Received: from ma.sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 26JFWe8f021216 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Tue, 19 Jul 2022 15:32:40 GMT In-Reply-To: (Alan Mackenzie's message of "Tue, 19 Jul 2022 15:01:12 +0000") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham 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:292276 Archived-At: Alan Mackenzie writes: > Hello, Eli. > > On Tue, Jul 19, 2022 at 15:39:11 +0300, Eli Zaretskii wrote: >> > Date: Tue, 19 Jul 2022 10:52:08 +0000 >> > From: Alan Mackenzie > >> > Hello, Emacs. > >> > Forgive me if I've asked this before, but how does one determine what >> > file a library has been loaded from? In particular, whether that file >> > is a source file, a byte compiled file or a native compiled file. > >> > I've tried looking at load-history, and it tells me cc-engine was loaded >> > from > >> > "/home/acm/emacs/emacs.git/sub-master-5/lisp/progmodes/cc-engine.elc" > >> > .. I think that's a lie. I suspect I'm dealing with a native compiled >> > cc-engine, here. In fact, the string ".eln" doesn't occur anywhere in >> > load-history, and I _know_ some of the files are native compiled - my >> > build was configured with-native-compilation. > >> > So, how do I find this out? > >> What do you like to find? whether it was loaded from cc-engine.elc or >> cc-engine-XXXXXX.eln? > > Exactly that, yes. > >> If so, why does it matter? > > It matters a great deal. There's the purely philosophical point that one > should be able to control and understand ones own Emacs. A further point > is that Emacs should not deceive its users. > > There's the point that if you're doing benchmark timings, the results are > meaningless if you don't know what you're timing. > > The reason I asked was I was seeing a bug in what I suspected to be a > ..eln, but didn't see it in .elc's, and thus suspected a native compiler > bug. I've seen other things since, and don't suspect that any more. > > But I'd still like to be able to know what file I'm executing. We coudln't change the `load-history' content as unfortunatelly it was breaking many packages (tested). If you have a native compiled function (say `find-file') to get the eln file containing it one can use. (native-comp-unit-file (subr-native-comp-unit (symbol-function #'find-file))) Hope it helps Andrea