🚀 go-pugleaf

Noah Friedman suggests:
>    If emacs is crashing with a "fatal error," it should be reported
> to bug-gnu-emacs@prep.ai.mit.edu.  Make sure you describe exactly what you
> did to crash emacs and also give the version of emacs you're using. 

Sorry if I seem irresponsible, but "exactly what I did" is just not that
easy to characterize.  The lightning bolt seems related to vm and to 
deleting buffers, but that is only a feeling.  I cannot predict when it
will happen nor recreate the occurrence, and I honestly don't think I can
make an effective bug report.

Starting a few days ago, I have been running vm in its own copy of emacs, and
it seems to be occurring less often.  This helps me breathe easier, but 
probably doesn't help get the bug fixed, alas.  Someday I'll get the courage
to play with the core file.

>    Also, if you report fatal errors that VM has caused when you post to
> this group it may also be useful to let everyone know which version of
> emacs you're using.  That way we'll know what to avoid and in what versions
> this is significant.

I did this twice in another string, so didn't want to repeat this ad nauseum.
But here goes again:

Vitals:
running HP 9000/345 under HP-UX 7.0
emacs version 18.55  (with lots of goodies from the net added)
problem has occurred on vm version 5.23 - 5.28
  (NO problem under 4.42, and, I believe, none yet under 5.29)

If anyone else has recently experienced a "Fatal error(6)" in emacs,
please speak up.

- Len Weisberg - HP Corp Computing & Services - weisberg@corp.HP.COM