You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using your Docker images to test one of my projects in CI, and I find that the current flycheck/emacs-cask:25.3 image's emacs crashes when executed. You can reproduce like so:
Edit: Actually emacs --version works, but just emacs doesn't work, and neither does the execution used in my test, which is emacs -Q -L . --eval '(setq byte-compile-error-on-warn t)' -batch -f batch-byte-compile <project el files>.
Also I should note that the 26.2 image (ID 2ff0c2eb4547) works, but the 24.5 image (ID 0d36fd8cbfd5) does not.
The text was updated successfully, but these errors were encountered:
Yes indeed, I can reproduce on my machine. These images work on Travis though, and that is also where they are built. So it may be caused by something in the environment that differs?
I don't have time to investigate, but I welcome solutions.
@carrete yes, but as Travis uses an outdated docker version, we can build them fine without disabling ASLR. Also, Emacs 27.1 and up have a portable dumper.
Anyway, I cannot reproduce the segfault with the latest images. Feel free to reopen if the issue strikes again.
I'm using your Docker images to test one of my projects in CI, and I find that the current
flycheck/emacs-cask:25.3
image's emacs crashes when executed. You can reproduce like so:The image's ID is
9a7c34abb84e
.Edit: Actually
emacs --version
works, but justemacs
doesn't work, and neither does the execution used in my test, which isemacs -Q -L . --eval '(setq byte-compile-error-on-warn t)' -batch -f batch-byte-compile <project el files>
.Also I should note that the 26.2 image (ID
2ff0c2eb4547
) works, but the 24.5 image (ID0d36fd8cbfd5
) does not.The text was updated successfully, but these errors were encountered: