I'd be willing to look at a copy, or if you can just send it to
mutt-dev, that would be even better. Perhaps the best thing to do would
be to make a mailbox with just that message and gzip it to avoid any
changes during transport, and send it as an attachement. Also, it would
be helpful to see a stack trace of the core dump if you have the core
handy: just run "gdb /path/to/mutt /path/to/core" making sure to specify
the same copy of mutt that produced the core, and type "where". The
same procedure works with dbx if you don't have gdb. Additionally, the
output of "mutt -v" is often a helpful debugging aid.
-Daniel
On Thu, Sep 30, 1999 at 12:14:04PM -0500, MSCS Technician <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I upgraded our Solaris 7 machine from mutt 0.95.4i to mutt 1.0pre3i
> following the recent security announcement.
>
> We've noticed that when one of our users sends a message from Solaris
> 7's dtmail, I can read the message in mutt, but attempts to 'r'eply wind up
> in a mutt segfault.
>
> We've duplicated this a number of times now, to be sure it wasn't
> somehow a corrupted message. I'd be willing to bounce it to anyone
> who wishes to take a look. Curious, messages sent from the user
> using mailx can be replied to just fine. We can also reply to those
> dtmail sent messages using dtmail; but mutt continues to segfault.
>
> Both 0.95.4i and 1.0pre3i were built on Solaris 7 with egcs 1.1.2.
> We didn't have this problem with 0.95.4i.
>
>
> Can anyone help?
>
>
> -Robert
>
> --
> --- \*/ ---
> Robert S. Dubinski, Computer Systems Technician, MSCS Dept. Marquette University
> Email: [EMAIL PROTECTED] Web: http://www.mscs.mu.edu/~tech
>
--
Daniel Eisenbud
[EMAIL PROTECTED]
