Indeed, I experienced the same issues when I followed his instructions literally.
This happens because, apparently, the system distribution he's currently using has `ulimit -c unlimited' already run for his current shell and "/proc/sys/kernel/core_pattern" with the phrase/word "core" inside. You can either do something similar to what I described in my reply to his suggestion or do as I just told in the previous paragraph, like so: --8<---------------cut here---------------start------------->8--- sudo -i echo "core" > "/proc/sys/kernel/core_pattern" exit ulimit -c unlimited emacs # ... and now it crashes and "core" is dumped at your current working # directory --- your user's home by default. # Now I suggest you to exit this shell, this will set # `ulimit -c' back to 0, disabling "core dumps". --8<---------------cut here---------------end--------------->8--- Just to note that, in the reply I gave to his message, I forgot to mention that I had to copy the contents of the first "wrapper" script to a place where I can edit it, so I could make something similar to the "gdb_cmds.txt" file. The first "wrapper" script can be found by doing: --8<---------------cut here---------------start------------->8--- which emacs --8<---------------cut here---------------end--------------->8--- Mason Hock <masonh...@gmail.com> writes: > Thanks for your response. > > I get > >> gdb $(which emacs) ./core > "/home/mason/.guix-profile/bin/emacs": not in executable format: File > format not recognized > /home/mason/./core: No such file or directory. > >> (gdb) bt > No stack. > > Mason
