lastquestion/explain-pause-mode

[native-comp branch] not top level in wrap-native for #<subr read-key-sequence-vector> (duplicate #65)

yantar92 opened this issue · 4 comments

Explain-pause-mode: please report this bug by creating a Github
issue at https://github.com/lastquestion/explain-pause-mode. Explain-pause-mode
is now disabled so you can continue to hopefully use Emacs. Info follows:

explain-pause version: 0.1
emacs version: 28.0.50

not top level in wrap-native for #
current
#s(explain-pause-command-record root-emacs nil nil 220804 (24347 38889 59780 614000) nil nil nil nil 0)

Backtrace:
(explain-pause-report-measuring-bug "not top level in wrap-native for #<subr read-key-s..." "current" #s(explain-pause-command-record :command root-emacs :native nil :parent nil :executing-time 220804 :entry-snap (24347 38889 59780 614000) :too-slow nil :is-profiled nil :under-profile nil :profile nil :depth 0))
(explain-pause--wrap-native # "C-c-" nil t)
(apply explain-pause--wrap-native # ("C-c-" nil t))
(read-key-sequence-vector "C-c-" nil t)
(read-key "C-c-")
(boon-c-god)
(# boon-c-god)
(apply # boon-c-god)
(funcall-interactively boon-c-god)
(command-execute boon-c-god)

This an many other errors are popping up when using native-comp branch of Emacs.

Here is another example:

Debugger entered--Lisp error: (wrong-type-argument characterp "  (explain-pause-report-measuring-bug \"not top lev...")
  (char-to-string "  (explain-pause-report-measuring-bug \"not top lev...")
  (org-agenda-get-restriction-and-command nil)
  (#f(compiled-function (&optional arg org-keys restriction) (interactive "P") #<bytecode -0x1c68e98405cf29a6>) nil nil nil)
  (ad-Advice-org-agenda #f(compiled-function (&optional arg org-keys restriction) (interactive "P") #<bytecode -0x1c68e98405cf29a6>) nil)
  (apply ad-Advice-org-agenda #f(compiled-function (&optional arg org-keys restriction) (interactive "P") #<bytecode -0x1c68e98405cf29a6>) nil)
  (org-agenda nil)
  (#<subr funcall-interactively> org-agenda nil)
  (apply #<subr funcall-interactively> (org-agenda nil))
  (funcall-interactively org-agenda nil)
  (command-execute org-agenda)

Explain-pause-mode: please report this bug by creating a Github
issue at https://github.com/lastquestion/explain-pause-mode. Explain-pause-mode
is now disabled so you can continue to hopefully use Emacs. Info follows:

explain-pause version: 0.1
emacs version: 28.0.50

not top level in wrap-native for #
current
#s(explain-pause-command-record root-emacs nil nil 13524 (24347 57304 189272 572000) nil nil nil nil 0)

Backtrace:
(explain-pause-report-measuring-bug "not top level in wrap-native for #<subr read-char-..." "current" #s(explain-pause-command-record :command root-emacs :native nil :parent nil :executing-time 13524 :entry-snap (24347 57304 189272 572000) :too-slow nil :is-profiled nil :under-profile nil :profile nil :depth 0))
(explain-pause--wrap-native #)
(apply explain-pause--wrap-native # nil)
(read-char-exclusive)
(org-agenda-get-restriction-and-command nil)
(#f(compiled-function (&optional arg org-keys restriction) (interactive "P") #<bytecode -0x1c68e98405cf29a6>) nil nil nil)
(ad-Advice-org-agenda #f(compiled-function (&optional arg org-keys restriction) (interactive "P") #<bytecode -0x1c68e98405cf29a6>) nil)
(apply ad-Advice-org-agenda #f(compiled-function (&optional arg org-keys restriction) (interactive "P") #<bytecode -0x1c68e98405cf29a6>) nil)
(org-agenda nil)
(# org-agenda nil)
(apply # (org-agenda nil))
(funcall-interactively org-agenda nil)
(command-execute org-agenda)

Hi @yantar92 , thanks for reporting this!

This is a duplicate of #65, and I'm pretty sure the root cuase is because native-comp branch doesn't honor the advice-add. Please follow me over there to that issue. :_)

If you have time, I have a hypothetical reduced repro that should verify my theory. I meant to try and build native-comp branch myself and file a bug, but I haven't had time yet.

Closing this as duplicate