Closed kaushalmodi closed 8 years ago
Emacs byte-code isn't stable between versions. It looks like esup
is struggle with a newer version of byte code.
Please post the contents of *esup-log*
. It probably won't appear by default, but it does exist.
Thanks for looking into it.
Here are links to stuff that might help with the debug:
For what it's worth, I saw this too:
Debugger entered--Lisp error: (void-variable defalias)
eval(defalias)
esup-child-profile-sexp(51461 51469 1)
esup-child-profile-buffer(#<buffer smartparens.elc> 1)
esup-child-profile-file("smartparens" 1)
esup-child-profile-sexp(4572 4594 0)
esup-child-profile-buffer(#<buffer init.el> 0)
esup-child-profile-file("/home/wilfred/.emacs.d/init.el" 0)
esup-child-run("/home/wilfred/.emacs.d/init.el" "50454")
eval((esup-child-run "/home/wilfred/.emacs.d/init.el" "50454"))
command-line-1(("-L" "/home/wilfred/.emacs.d/elpa/esup-20150519.1701/" "-l" "esup-child" "--eval=(esup-child-run \"/home/wilfred/.emacs.d/init.el\" \"50454\")"))
command-line()
normal-top-level()
Deleting all the smartparens/*.elc files and bytecompiling afresh does not help.
Ok, I'll investigate. The tricky part is isolating the issue.
On Tue, Sep 29, 2015 at 5:14 PM, Wilfred Hughes notifications@github.com wrote:
For what it's worth, I saw this too:
Debugger entered--Lisp error: (void-variable defalias) eval(defalias) esup-child-profile-sexp(51461 51469 1) esup-child-profile-buffer(#
1) esup-child-profile-file("smartparens" 1) esup-child-profile-sexp(4572 4594 0) esup-child-profile-buffer(# 0) esup-child-profile-file("/home/wilfred/.emacs.d/init.el" 0) esup-child-run("/home/wilfred/.emacs.d/init.el" "50454") eval((esup-child-run "/home/wilfred/.emacs.d/init.el" "50454")) command-line-1(("-L" "/home/wilfred/.emacs.d/elpa/esup-20150519.1701/" "-l" "esup-child" "--eval=(esup-child-run \"/home/wilfred/.emacs.d/init.el\" \"50454\")")) command-line() normal-top-level() Deleting all the smartparens/*.elc files and bytecompiling afresh does not help.
— Reply to this email directly or view it on GitHub https://github.com/jschaf/esup/issues/25#issuecomment-144193200.
I was able to reproduce this with (require 'dired-x)
enabled during profiling. Disabling debugging when profiling (https://github.com/jschaf/esup/pull/37) works around this issue.
Can you give it a try now that debugging is disabled?
I now get this error:
Debugger entered--Lisp error: (file-error "make server process failed" "Success" :name "esup-server" :type nil :server t :host local :service t :family nil :nowait t :stop nil :buffer "esup-log" :coding utf-8 :noquery t :filter esup--server-filter :sentinel esup--server-sentinel :log esup--server-logger) make-network-process(:name "esup-server" :type nil :server t :host local :service t :family nil :nowait t :stop nil :buffer "esup-log" :coding utf-8 :noquery t :filter esup--server-filter :sentinel esup--server-sentinel :log esup--server-logger) esup-server-create(t) esup(nil)
Looks like you are seeing the same issue too.
Currently, I am on the latest master build.
It looks like I was mistaken, and had dired-x
disabled while testing this, so evidently #37 doesn't work around the invalid byte-code issue. (Sorry @jschaf). I haven't seen the trace you mentioned on the latest master, however.
@kaushalmodi I found a work-around by removing the :nowait t, or setting it to nil. I'm still not exactly sure what changed in make-network-process
.
@jschaf Thanks! That worked for me too. I'll close this issue as the fix seems to be done in the master. But if removing :nowait t
works for any emacs version, please commit that.
Glad it worked. I'll change it tonight.
Hi,
I haven't tried
M-x esup
in earlier versions but in versions 24.5 (latest stable as of now) and the latest build from git master branch (25.x), I get this error: