Re: disappearing program

[Alex Schroeder]

I think Eli's observation cleared it all up.  The kernel killed Emacs
because of an out-of-memory condition.

Richard Stallman <address@hidden> writes:

>     Today I had the weirdest bug.  I was going through a collection of
>     JPEG images (each a little bit below half a megabyte), opening an
>     image (and viewing it with auto-image-file-mode), killing the buffer,
>     sometimes reopening images I had already looked at, etc.  Suddenly
>     Emacs dies.
>
> What precisely happened?  How did it "die"?

The window just disappeared.

>     DISPLAY = :0.0
>     TERM = rxvt
>     Breakpoint 1 at 0x80d413a: file emacs.c, line 414.
>     Breakpoint 2 at 0x80b8da2: file xterm.c, line 12519.
>     (gdb) c
>     Continuing.
>
>     Program terminated with signal SIGKILL, Killed.
>     The program no longer exists.
>     (gdb) bt
>     No stack.
>
> Did you type `c' after Emacs "died", or did it "die"
> after you typed `c'?

I use the following shell script to start Emacs:

#! /usr/bin/zsh
cd /usr/local/src/emacs/src
emacs -geometry 150x55 &
aterm -e gdb program $! &

Thus, gdb attaches itself to the Emacs process, and I have to hit c
for Emacs to complete its startup.  A long time elapsed between the c
for continue and the following message.

Alex.