How to stop emacs server

Your .profile should be loaded when you log in, not in each terminal. Its purpose is to define environment variables and other settings for the whole session (including your window manager and any program you start from it such as Emacs). It's normal that ~/.profile isn't read when you start a terminal: it's rare to need to define environment variables then. Your shell has an initialization file (.bashrc or .zshrc or similar file), usually used to define functions and aliases and set shell options.

On .profile, its cousins and how they are loaded, read this answer and the ones I link to. All systems have a way to set environments variables when you log in, but there is some variation as to how (a lot of environments read .profile, but some such as yours don't).

I've had some luck with attaching gdb to the running process. Borrowing heavily from: How to attach terminal to detached process?

write-file

1. mkfifo /tmp/some_name
2. gdb -p [pid]
3. (within gdb): call close(0)
4. (within gdb): call open('/tmp/some_name', 0600). At this point gdb will appear to hang
5. (from the shell): echo '(write-file "savedresults")' > /tmp/some_name
6. (within gbd): ctrl-d

The contents of scratch are written out to the file 'savedresults'. Interestingly (write-file "savedresults") is appended to the file (unsure why).

C-x C-w name

1. mkfifo /tmp/some_name
2. gdb -p [pid]
3. (within gdb): call close(0)
4. (within gdb): call open('/tmp/some_name', 0600). At this point gdb will appear to hang
5. (from the shell): cmd="^X^Wsavedresults" (input ^X via key sequence: CTRL-V CTRL-X, similar for ^W"
6. (from the shell): echo "$cmd" > /tmp/some_name
7. (within gbd): ctrl-d

Contents are written to file 'savedresults'.