[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help debugging a backtrace
From: |
Michael Heerdegen |
Subject: |
Re: Help debugging a backtrace |
Date: |
Sun, 01 May 2016 22:45:58 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.93 (gnu/linux) |
Hi Kaushal,
thanks for the update...interesting.
In addition to your strategies, you might want to try something like
#+begin_src emacs-lisp
(advice-add 'require :before
(lambda (feature &optional filename _noerror)
(when (or (eq feature 'finder-inf)
(and (stringp filename)
(string-match-p "finder-inf" filename)))
(debug))))
#+end_src
at the beginning of your (outer) config file. This pops up the debugger
as soon as "something" tries to `require' finder-inf.
In my setup, the debugger pops up with this content for example:
,----------------------------------------------------------------------
| require(finder-inf nil t)
| package-built-in-p(late-night-theme (0 0))
| package-activate(late-night-theme)
| package-initialize()
| byte-code[...]
| load("~/gnu-emacs/.gnu-emacs")
| eval-buffer(#<buffer *load*> nil "/home/micha/.emacs" nil t) ; Reading at
buffer position 261
| load-with-code-conversion("/home/micha/.emacs" "/home/micha/.emacs" t t)
| load("~/.emacs" t t)
| [...]
| command-line()
| normal-top-level()
`----------------------------------------------------------------------
It would be interesting to see what happens at/after this moment in your
case, e.g. what's the value of `load-file-name' etc. (use R to eval stuff
from the debugger)
Good luck,
Michael.
- Re: Help debugging a backtrace, Michael Heerdegen, 2016/05/01
- Re: Help debugging a backtrace, Michael Heerdegen, 2016/05/01
- Re: Help debugging a backtrace, Kaushal Modi, 2016/05/01
- Re: Help debugging a backtrace,
Michael Heerdegen <=
- RE: Help debugging a backtrace, Drew Adams, 2016/05/01
- Re: Help debugging a backtrace, Kaushal Modi, 2016/05/02
- Re: Help debugging a backtrace, Kaushal Modi, 2016/05/02
- Re: Help debugging a backtrace, Michael Heerdegen, 2016/05/02
- Re: Help debugging a backtrace, Kaushal Modi, 2016/05/02
- Re: Help debugging a backtrace, Eli Zaretskii, 2016/05/02