From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.bugs Subject: bug#46256: [feature/native-comp] AOT eln files ignored if run from build tree Date: Mon, 8 Mar 2021 05:54:28 +0000 Message-ID: References: <86eehujcip.fsf@gmail.com> <86blch14qt.fsf@gmail.com> <83h7m84h9g.fsf@gnu.org> <86v9ao5czu.fsf@gmail.com> <86wnutogrh.fsf@gmail.com> <86wnut8fb9.fsf@gmail.com> <861rd1tbpa.fsf@gmail.com> <83pn0km6y3.fsf@gnu.org> <86ft1f8ara.fsf@gmail.com> <83sg5cjdn8.fsf@gnu.org> <83r1kwjcy2.fsf@gnu.org> <8335x6u9o4.fsf@gnu.org> <83zgzesrku.fsf@gnu.org> <83tupms4mp.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6279"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 46256@debbugs.gnu.org, andrewjmoreton@gmail.com, Andrea Corallo To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Mar 08 06:56:33 2021 Return-path: Envelope-to: geb-bug-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 1lJ8sb-0001Wt-0Q for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 08 Mar 2021 06:56:33 +0100 Original-Received: from localhost ([::1]:50762 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lJ8sZ-0001yp-VQ for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 08 Mar 2021 00:56:31 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46548) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lJ8s6-0001yf-Ro for bug-gnu-emacs@gnu.org; Mon, 08 Mar 2021 00:56:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58591) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lJ8s6-0002N4-Jp for bug-gnu-emacs@gnu.org; Mon, 08 Mar 2021 00:56:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lJ8s6-0004vv-Hb for bug-gnu-emacs@gnu.org; Mon, 08 Mar 2021 00:56:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Pip Cet Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 08 Mar 2021 05:56:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46256 X-GNU-PR-Package: emacs Original-Received: via spool by 46256-submit@debbugs.gnu.org id=B46256.161518291618904 (code B ref 46256); Mon, 08 Mar 2021 05:56:02 +0000 Original-Received: (at 46256) by debbugs.gnu.org; 8 Mar 2021 05:55:16 +0000 Original-Received: from localhost ([127.0.0.1]:41904 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lJ8rM-0004uq-6L for submit@debbugs.gnu.org; Mon, 08 Mar 2021 00:55:16 -0500 Original-Received: from mail-oo1-f52.google.com ([209.85.161.52]:37755) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lJ8rG-0004uV-SB for 46256@debbugs.gnu.org; Mon, 08 Mar 2021 00:55:15 -0500 Original-Received: by mail-oo1-f52.google.com with SMTP id e17so1942554oow.4 for <46256@debbugs.gnu.org>; Sun, 07 Mar 2021 21:55:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=alcecVUzGGwCqa0c7RL4pyuWwuv366RWup6KwF9xDXQ=; b=LpX2VLKT9stvIct/uej1BatW5zPO/IFxXmE8J/FvnhcfZDT1hi6D47qBvxu/5l7aJ2 BnvYxbm88TSb2u7nwOmXYzu7FL83P+jeUjfgDNB+jT3/YCe7UcHfnPptot3KoGZm29fw klwMbG8Ph812lh1qxYRBDrbTKTthjypv3HwMODWhUj3+8P/qsiGArTX197VoHb6PFYG/ EGUonj1CGi2fHwTzZA8OuZLNmPzH8eKIKMrk78nodWyuKrWfPwMKvp4svvK6LmbjhtSB rCElPe15oIUCsJgAEjFYBqqNN8NrcTmQ8Zp/Ghav+/HNNaVVNE1qFxpjKRdExF6x1HK7 DueA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=alcecVUzGGwCqa0c7RL4pyuWwuv366RWup6KwF9xDXQ=; b=VgdLefRi/T1TdS4Zxa8U81tyjn5NGwIFUuIrnuMzCTLOWg10O2yGjllqTmfoMcNlYq Cd/HMiwaBytz1ul7VK4o40+dqjWw21l1k0XCtCBmQUOW3kjrBHTWGsYdB5ZAhC+brZkc Ky8DMr/cI3q45Jwe7Gmmz0ZyyU1FwXmsw2dZB84h4YhInAtiKadp8PFmJyP3QX4zGq+v 4vMjvMZ8C3c1KjlG0FP+osr9QAgybDGNgoUhGNLJGjq+TICCai6UKtK8DvR2PT1h7BIo mU9O4auSvtdhwc2wOgZ9+Z9HSkE/2uGBjek22Aca37cA9D2qynVvpt11rsIRM9k2SUCL l87w== X-Gm-Message-State: AOAM531dRvHYEU+VdWtmxFqxj06R4mTuDF55CId6RrFhXhjpN9dTjurv LZY9EaHsuUx7DHqf9vnxJfnoDYaXwb4IALwjpQg= X-Google-Smtp-Source: ABdhPJxblkTd5OQkjImyZrJBJRQGZXuXSuPSQZX5qwt12l7ZLrp+kJUlNU+ZjZjNKeaq5C2IWliYo4xSAhOElB/8XyY= X-Received: by 2002:a4a:2511:: with SMTP id g17mr17675104ooa.22.1615182905030; Sun, 07 Mar 2021 21:55:05 -0800 (PST) In-Reply-To: <83tupms4mp.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:201805 Archived-At: On Mon, Mar 8, 2021 at 3:31 AM Eli Zaretskii wrote: > > From: Andrea Corallo > > Cc: Eli Zaretskii , 46256@debbugs.gnu.org, > > andrewjmoreton@gmail.com > > Date: Sun, 07 Mar 2021 21:51:15 +0000 > > > > > Why wouldn't it be? I'm trying to follow along here :-) > > > > If the CU was GC'ed the eln should have been dlclosed. If that's the > > case at the next load we should get a fresh handle and 'saved_cu' should > > be NULL (ops! Qnil... :/) because static allocated. > > > > Here what we see is that we are loading two times without dlclosing and > > the object pointed by 'cu_saved' has some issue. > > > > So thinking about: the fact that the eln was never dlclosed should be > > prove that the CU was not GC'ed and so I was wrong. This suggests also > > that before further talking stupid I'd better say I'm done for the day > > :) > > Thanks. Please tell me if you need me to provide some further data > from this crashed session. If not, I will end the debugging session Do you have to end the crashed session to start a new one? I think we should keep it open for a while longer (or create a core dump, if that works?) and still try to test whether it's the dynlib_close()-might-not-close bug. > and will try to find a recipe for reproducing the crash, so we could > see which of the guesses are true. Here's what I did to reproduce the crash: 1. create a file "test.el": ;; -*- lexical-binding: t; -*- (defun testfun (x) (1+ x)) 2. Evaluate: (require 'comp) (native-elisp-load (native-compile "test.el")) (testfun 3) (fmakunbound 'testfun) (garbage-collect) (native-elisp-load (native-compile "test.el")) Note that this might not always work because of conservative GC. Pip