From: "T.V Raman" <raman@google.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs:Native-Comp Backtrace
Date: Wed, 26 Aug 2020 08:06:27 -0700 [thread overview]
Message-ID: <p91v9h5cuq4.fsf@google.com> (raw)
In-Reply-To: <24389.44700.121870.344164@google.com> (T. V. Raman's message of "Tue, 25 Aug 2020 17:36:44 -0700")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 3034 bytes --]
"T.V Raman" <raman@google.com> writes:
Here is some more info based on a work-around:
Conjecture: native-comp has issues with with-eval-after-load and
friends:
The following setup produced the afore-mentioned error:
1. In the emacs startup, load dired-x when dired is loaded:
(with-eval-after-load "dired" (require 'dired-x))
2. dired-mode-hook contains dired-omit-mode defined in dired-x
3. During startup, a dired buffer is opened -- either via psession,
desktop or some other means
With the above, you get the error (symbol's function definition is
void: dired-omit-mode)
Fix: If in the startup file, you remove the with-eval-after-load and
simply require dired-x, then it works.
Additional info which lends credence to the conjecture:
Emacspeak loads module-specific code using eval-after-load e.g. when
"ido" is loaded, it loads emacspeak-ido after ido is done loading. In
native-comp emacs, I find that (featurep 'emacspeak-ido) is nil after
ido is loaded.
I suspect use-package may also be affected in a similar way.
> Hi Andrea and others,
>
> This is a follow-on to my earlier message re a possible race
> condition, this time with a backtrace.
>
> 1. I load dired-x in my emacs startup, and I have dired-omit-mode
> enabled via customize (settings saved to a custom file)
>
> 2. The above emacs startup works with no errors or warnings with
> regular emacs.
>
> 3. With emacs native-comp version, this throws a symbol's value
> as variable is void in the *Messages* buffer.
> 4. native-emacs (native comp version) does not throw a
> backtrace even if you start it as native-emacs
> --debug-init
>
> 5. I produced the attached backtrace by setting
> debug-on-error to t at the top of my early-init.el
> 6. As the backtrace below shows, the psession package
> in the process of restoring buffers opens a dired
> buffer, and at that point, dired-omit-mode is on
> dired-mode-hook, but apparently dired-x hasn't been
> fully loaded yet.
>
> Debugger entered--Lisp error: (void-function dired-omit-mode)
> (dired-omit-mode)
> (run-hooks change-major-mode-after-body-hook dired-mode-hook)
> (apply run-hooks (change-major-mode-after-body-hook dired-mode-hook))
> (run-mode-hooks dired-mode-hook)
> (dired-mode "~/Mail/foo" "-al")
> (dired-internal-noselect "~/Mail/foo" nil)
> (dired-noselect "~/Mail/foo")
> (run-hook-with-args-until-success dired-noselect "~/Mail/foo")
> (find-file-noselect "/home/raman/Mail/foo/" nowarn)
> (psession--restore-some-buffers)
> (run-hooks emacs-startup-hook term-setup-hook)
> (#f(compiled-function () #<bytecode -0x11887347ec248cf1>))
> (normal-top-level)
>
> --
> 7©4Id: kg:/m/0285kf1 0Ü87©4
--
7©4Id: kg:/m/0285kf1 0Ü87©4
next prev parent reply other threads:[~2020-08-26 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 0:36 Emacs:Native-Comp Backtrace T.V Raman
2020-08-26 15:06 ` T.V Raman [this message]
2020-08-26 19:09 ` Andrea Corallo via Emacs development discussions.
2020-08-26 19:32 ` T.V Raman
2020-08-26 19:46 ` Andrea Corallo via Emacs development discussions.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p91v9h5cuq4.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).