Can you attach to the process with gdb and get a stack trace? That
would be helpful.
Also, bug reports are much more useful when they include "mutt -v"
output. Especially since this might or might not be a bug in your
curses library, we need to know which curses library you use.
-Daniel
On Mon, Mar 22, 1999 at 09:33:04PM -0500, Marsh Ray <[EMAIL PROTECTED]> wrote:
> I have seen this on Debian Linux (slink) as well.
>
> On Mon, Mar 22, 1999 at 12:52:07PM -0800, Russell Van Tassell wrote:
> >
> > I would appear as if Mutt 0.95.4i will "run away" on a Solaris 2.5.1
> > machine if the terminal disappears from it (like a couple of other
> > well-known Solaris tools). Instead of receiving the HUP from the
> > parent shell, the process gets backgrounded and attached to init where
> > it drives the CPU load up (clearly something it probably should not
> > do in any case).
> >
> > Help? Ideas?
>
>
--
Daniel Eisenbud
[EMAIL PROTECTED]
