Re: mutt/libc? problems after recent sid upgrade

[Lee Bradshaw <lee@sectionIV.com>]

Thanks for the quick response Bart. I stripped my ~/.muttrc down to the
single line that was causing the problem. Do you see anything wrong with
this?

  freefall ~ $ cat .muttrc
  # Change "Re: Re: ..." to "Re: ..."
  set reply_regexp="^((((fwd|aw|re(([0-9]|[[0-9]+])?)):[ \t]*)*)[ \t]*)+"

As I said before, this works fine with the same version of mutt, but
slightly earlier libraries.

On Thu, Jan 09, 2003 at 01:01:18PM -0500, Bart Trojanowski wrote:
> I am running sid's lctest mutt and I don't see this.
> 
> * Lee Bradshaw <lee@sectionIV.com> [030109 12:24]:
>> strace from a segmentation fault on the console is available at
>> 
>>   http://www.mindspring.com/~lee.bradshaw/mutt2.log
> 
> From the log files you provided....
> 
> <snip>
> access("/home/lee/.muttrc", F_OK)       = 0
> write(1, "...") = 52
> ioctl(2, SNDCTL_TMR_STOP, {B1000000 -opost -isig -icanon echo ...}) = -1 ENOTTY (Inappropriate ioctl for device)
> open("/home/lee/.muttrc", O_RDONLY)     = 3
> fstat64(3, {st_mode=S_IFREG|0644, st_size=8344, ...}) = 0
> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40012000
> read(3, "# The first two variables are no"..., 4096) = 4096
> <snip>
> 
> Since the last thing I see that actually makes any sense is parsing of
> the muttrc, would it be possible to see the first few lines of your
> muttrc file?
> 
> Maybe I can reproduce it.
> 
> Cheers,
> Bart.
>