On Thu, Oct 07, 1999 at 09:13:20AM +0200, Thomas Roessler wrote:
> On 1999-10-07 00:04:25 +0200, [EMAIL PROTECTED] wrote:
>
> > Ok, I tried today with several combinations. Removing .muttrc (with
> > my my_hdr settings) did not change a thing, just like removing
> > _any_ header. However, inserti
On 1999-10-07 00:04:25 +0200, [EMAIL PROTECTED] wrote:
> Ok, I tried today with several combinations. Removing .muttrc (with
> my my_hdr settings) did not change a thing, just like removing
> _any_ header. However, inserting the Message-Id: field _did_ cure
> the problem: I could reply again! So,
On Tue, Oct 05, 1999 at 09:54:55PM +0200, Thomas Roessler wrote:
> The behaviour you observe means most probably that we have some rare
> problem when reading user headers from the edited file. Since you
> seem to be able to reproduce this problem, could you please give us
> a mail message which
and lists settings?
On 1999-10-05 20:48:22 +0200, [EMAIL PROTECTED] wrote:
> Date: Tue, 5 Oct 1999 20:48:22 +0200
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: mutt segfaults + gdb output
> Reply-To: Rutger Nijlunsing <[EMAIL PROTECTED]>
>
> Hi *,
>
Hi *,
My mutt 1.0pre2i on Solaris segfaults after pressing 'y' to send a
reply to a mail. The mail to which I'm replying might miss some
required headers.
gdb gives:
Program received signal SIGSEGV, Segmentation fault.
0xef6ce0a4 in strchr ()
(gdb) up
#1 0x88af4 in encode_headers (h=0xede68) a
