Re: runaway proc...

JAT> I did rebuild with debug and full error-checking, so I was ready the JAT> next time it went crazy. However, yet again it left a useless core. JV> Try running it directly under gdb directly. ok, I've been doing this for several days, and when the problem occurs I get one of two things: o all XEmacs frames disappear, a msg appears in the window I started gdb saying: Error: Object "(null)" does not have windowed ancestor gdb is still running, and I can re-start XEmacs (I don't mean continue - I really mean "run" again) o XEmacs stops, and gdb is completely lost as to where it is - the stack is just "??" - in this case I have to quit gdb and start completely from scratch these are occurring almost exclusively while using VM (I typically run at least two instances of XEmacs, one dedicated to VM - it's those that are crashing) I think it's most often when opening a new frame in which to view a folder, quitting from a folder (I have vm-frame-per-summary set to t), etc. obviously something very bad is happening - sorry this isn't more informative -- John A. Turner, Senior Research Associate Blue Sky Studios, One South Rd, Harrison, NY 10528 http://www.blueskystudios.com/ (914) 381-8400