Repository navigation
Emacs and core dumps #115
Description
Activity
Yes but it shouldn't be, is it? Maybe we missed one of the versions..
I compiled emacs25-25.3nb8 from commit 28aa778 for reference. I am using X11 over SSH, in case that introduces any other known issues. I will rebuild everything from scratch in a new zone and test just to make sure I haven't done something wrong/weird.
Ah ok, if you compiled yourself outside of a pkgbuild image (https://github.com/joyent/pkgsrc/wiki/pkgdev:setup) then it will likely be linked against libumem. The logic that excludes emacs is here: https://github.com/joyent/pkgbuild/blob/master/include/libumem.mk
Thank you. I compiled myself bc I am on OmniOS CE. I will try doing pkgbuild image.
I can't figure out how to get pkgbuild to work on OmniOS CE. It's not officially supported. Is there some simple way I can just patch the build itself within pkgsrc? Maybe I'll just move to SmartOS.
Hm, if you're compiling yourself it may just be leaking from a dependency, you can use
ldd -sto see where the libumem dependency is coming from. If it's still coming directly from emacs somehow, you could addBUILDLINK_TRANSFORM+= rm:-lumemto the pkgsrc emacs Makefile which will strip any-lumemflags from the compiler.Ok thank you. There's a ton of of deps that bring libumem in. I removed them and I am going to try and build with that Makefile option and see what happens.
Well I pretty much rebuilt the entire userland without libumem and manages to get emacs to build without it. Now when I run it, I get:
emacs: Memory exhausted--use M-x save-some-buffers then exit and restart EmacsAnd it dies. I've done all I can do.
I'm just going to use SmartOS. I assume it works correctly there.
- added a commit that references this issue
on Aug 28, 2018 - added a commit that references this issue
on Sep 24, 2018 122 remaining items
- added 8 commits that reference this issue
on May 14, 2026 - added a commit that references this issue
on May 22, 2026 - added a commit that references this issue
on May 24, 2026 - added 2 commits that reference this issue
on Jul 14, 2026 - added 2 commits that reference this issue
on Sep 12, 2026
I know there is a long history with this, and maybe it will never be resolved, but is it still the assumed that Emacs is going core dump constantly due to it's linking to libumem? I can't go more than 10 or 15 minutes without a coredump. I just need to confirm that this is just a fact of life so I can either try to live with it or make any possible adjustments.