Bug#346073: Bug#277864: mutt segfault (fwd)
- Forwarded message from Hilmar Preusse <[EMAIL PROTECTED]> -
Date: Mon, 12 Mar 2007 13:21:33 +0100
From: Hilmar Preusse <[EMAIL PROTECTED]>
Reply-To: Hilmar Preusse <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
To: Christoph Berg <[EMAIL PROTECTED]>, Noah Meyerhans <[EMAIL PROTECTED]>,
Jeffery von Ronne <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
"Edward J. Shornock" <[EMAIL PROTECTED]>,
Alan BRASLAU <[EMAIL PROTECTED]>
Subject: Bug#277864: mutt segfault
On 06.03.07 Christoph Berg ([EMAIL PROTECTED]) wrote:
Hi all,
> Re: Hilmar Preusse 2006-01-04 <[EMAIL PROTECTED]>
> > I believe I see the same bug here. The bug occurs, when I use my IMAP
> > INBOX.
>
I still see segfaults, but I'm not really sure, if this is #277864.
Looks more like #346073.
The message index is incorrect. Try reopening the mailbox.*** glibc
detected *** corrupted double-linked list: 0x0826e690 ***
Aborted
Surprisingly the situation improves, if I tell mutt to use SSL to
connect to the IMAP server.
H.
--
sigmentation fault
- End forwarded message -
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
Bug#277864: mutt segfault
On 06.03.07 Christoph Berg ([EMAIL PROTECTED]) wrote: Hi all, > Re: Hilmar Preusse 2006-01-04 <[EMAIL PROTECTED]> > > I believe I see the same bug here. The bug occurs, when I use my IMAP > > INBOX. > I still see segfaults, but I'm not really sure, if this is #277864. Looks more like #346073. The message index is incorrect. Try reopening the mailbox.*** glibc detected *** corrupted double-linked list: 0x0826e690 *** Aborted Surprisingly the situation improves, if I tell mutt to use SSL to connect to the IMAP server. H. -- sigmentation fault -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#277864: mutt segfault
Re: Jeffery von Ronne 2007-03-06 <[EMAIL PROTECTED]>
> After experiencing the segfaults, I had switched from mutt's imap
> support to using offlineimap. I switched back to mutt's imap (current
> etch version on one machine, Ubuntu Edgy version on another) about two
> months ago and haven't experienced any segfaults.
Thanks.
> The closest thing I've experienced (which I should probably open a
> separate bug report on) is an occasionally freeze of the mutt process
> when trying to reconnect to the IMAP server after it has been disconnected.
[...]
Re: Noah Meyerhans 2007-03-06 <[EMAIL PROTECTED]>
> I see similar problems when reconnecting to a Cyrus IMAP server (the
> cert is valid). If I get disconnected from the server, it's not worth
> it to even try to reconnect; the attempt hangs every time.
>
> But that's a separate bug report. I haven't gotten around to filing
> that one yet. :)
That might be http://bugs.mutt.org/2717 which hasn't been reported to
Debian yet but which I'm pondering to fix in etch. So please report
it. (There is #196766 for POP which might be the same issue.)
(As I don't use IMAP regularly myself, I'd be glad for any help here.
I'll probably upload a new mercurial snapshot ("tip") to experimental
soon, or you could try that yourself.)
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
Bug#277864: mutt segfault
On Tue, Mar 06, 2007 at 10:14:40AM -0600, Jeffery von Ronne wrote: > The closest thing I've experienced (which I should probably open a > separate bug report on) is an occasionally freeze of the mutt process > when trying to reconnect to the IMAP server after it has been disconnected. > This is with a UW IMAP server that has an expired SSL certificate. I see similar problems when reconnecting to a Cyrus IMAP server (the cert is valid). If I get disconnected from the server, it's not worth it to even try to reconnect; the attempt hangs every time. But that's a separate bug report. I haven't gotten around to filing that one yet. :) noah signature.asc Description: Digital signature
Bug#277864: mutt segfault
On Tue, Mar 06, 2007 at 12:49:26PM +0100, Christoph Berg wrote: > I'm just digging through Debian's mutt bug list. Can anyone of you > still reproduce #277864 with recent mutt packages? At the moment > 1.5.13-1.1 is in etch/sid and 1.5.14+cvs20070301-1 in experimental. It > would be nice if you could give both a try and tell me which > works/doesn't work. After experiencing the segfaults, I had switched from mutt's imap support to using offlineimap. I switched back to mutt's imap (current etch version on one machine, Ubuntu Edgy version on another) about two months ago and haven't experienced any segfaults. The closest thing I've experienced (which I should probably open a separate bug report on) is an occasionally freeze of the mutt process when trying to reconnect to the IMAP server after it has been disconnected. This is with a UW IMAP server that has an expired SSL certificate. It usually happens if I'm composing a message in one instance of mutt and then startup another instance of mutt and open the same folder in that mutt. Then when I finish composing the message, mutt reports that it lost the imap lock on the folder and while trying to reconnect, prompts me whether I want to accept the expired certificate, if I say "accept" it freezes up and doesn't continue. (I think it locks up if I choose "reject" too, but I haven't tried that in a while.) Control-c doesn't work and the only thing I can do is kill the process externally. -- Jeff von Ronne -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#277864: mutt segfault
Re: Noah Meyerhans 2007-03-06 <[EMAIL PROTECTED]> > > I cannot reproduce the segfaults any longer with either version. Mutt is > > co-operating on both x86 (with an AthlonXP 1800+) and AMD64 (with a > > 4600+ X2). Hopefully others have the same experience and this bug can > > be closed... > > I've been using mutt in etch for several weeks now, and although I > have some vague recollection of a segfault in that time, I'm not > completely sure. The strange thing, though, even with sarge's mutt, > is that the crashes were really unpredictable. I could never > consistently reproduce them. Mutt would be fine for some time, maybe > up to one month (not the same process, but getting restarted e.g. when > I arrived at work each morning). But then it would go through a > period where it would crash several times a day for a few days. > > Given that it was so hard to reproduce this problem to begin with, I'm > hesitant to say that it's gone completely, but it seems like it might > be. Sorry I can't provide any more concrete info. Thanks for the replies. It seems that the behavior at least improved. I'm going to wait a few days to hear what the others report and then would like to close the bug - there's a couple of other imap-related segfaults reported, and given the plethora of recent imap fixes, chances are high that this is already fixed, or is related to the others. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Bug#277864: mutt segfault
Hello Christoph, I have tried both 1.5.13-1.1 (etch/sid) and 1.5.14+cvs20070301-1 (experimental) with three different IMAP mailboxes. Both versions seem to work correctly. (Since the filing of the bug report, I have been holding a downgraded version of mutt.) Thank you for your development work! Alan On Tuesday 06 March 2007 12:49, you wrote: > tags 277864 + moreinfo > thanks > > Re: Noah Meyerhans 2004-10-23 <[EMAIL PROTECTED]> > > > Hello. I have been experiencing mutt segfaults with annoying regularity > > lately. It seems to have to do with IMAP, and the backtrace from a core > > file seems to agree: > > > > (gdb) where > > #0 0x40263ffd in free () from /lib/libc.so.6 > > #1 0x080aade8 in safe_free (ptr=0x40322620) at lib.c:127 > > Re: Jeffery von Ronne 2005-11-28 > <[EMAIL PROTECTED]> > > > I've also been getting occasional IMAP related seg-faults. > > Re: Hilmar Preusse 2006-01-04 > <[EMAIL PROTECTED]> > > > I believe I see the same bug here. The bug occurs, when I use my IMAP > > INBOX. > > Re: Edward J. Shornock 2006-02-04 > <[EMAIL PROTECTED]> > > > I had the segfault problem as well while using IMAP at the "Sorting > > Folders" step. Upon downgrading to 1.5.11-5 the segfaults stopped. > > Re: Alan BRASLAU 2006-03-17 > <[EMAIL PROTECTED]> > > > Systematic segmentation fault upon opening an imap mailbox. > > Hi, > > I'm just digging through Debian's mutt bug list. Can anyone of you > still reproduce #277864 with recent mutt packages? At the moment > 1.5.13-1.1 is in etch/sid and 1.5.14+cvs20070301-1 in experimental. It > would be nice if you could give both a try and tell me which > works/doesn't work. > > Thanks, > Christoph -- Alan Braslau CEA DSM-DRECAM-SPEC CNRS URA 2464 Orme des Merisiers 91191 Gif-sur-Yvette cedex FRANCE tel: +33 1 69 08 73 15 fax: +33 1 69 08 87 86 mailto:[EMAIL PROTECTED] http://www-dna2006.cea.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#277864: mutt segfault
On Tue, Mar 06, 2007 at 08:45:02AM -0500, Edward Shornock wrote: > I cannot reproduce the segfaults any longer with either version. Mutt is > co-operating on both x86 (with an AthlonXP 1800+) and AMD64 (with a > 4600+ X2). Hopefully others have the same experience and this bug can > be closed... I've been using mutt in etch for several weeks now, and although I have some vague recollection of a segfault in that time, I'm not completely sure. The strange thing, though, even with sarge's mutt, is that the crashes were really unpredictable. I could never consistently reproduce them. Mutt would be fine for some time, maybe up to one month (not the same process, but getting restarted e.g. when I arrived at work each morning). But then it would go through a period where it would crash several times a day for a few days. Given that it was so hard to reproduce this problem to begin with, I'm hesitant to say that it's gone completely, but it seems like it might be. Sorry I can't provide any more concrete info. noah signature.asc Description: Digital signature
Bug#277864: mutt segfault
On Tue, Mar 06, 2007 at 12:49:26PM +0100, Christoph Berg wrote: > > Hi, > > I'm just digging through Debian's mutt bug list. Can anyone of you > still reproduce #277864 with recent mutt packages? At the moment > 1.5.13-1.1 is in etch/sid and 1.5.14+cvs20070301-1 in experimental. It > would be nice if you could give both a try and tell me which > works/doesn't work. I cannot reproduce the segfaults any longer with either version. Mutt is co-operating on both x86 (with an AthlonXP 1800+) and AMD64 (with a 4600+ X2). Hopefully others have the same experience and this bug can be closed... signature.asc Description: Digital signature
Bug#277864: mutt segfault
tags 277864 + moreinfo thanks Re: Noah Meyerhans 2004-10-23 <[EMAIL PROTECTED]> > Hello. I have been experiencing mutt segfaults with annoying regularity > lately. It seems to have to do with IMAP, and the backtrace from a core > file seems to agree: > > (gdb) where > #0 0x40263ffd in free () from /lib/libc.so.6 > #1 0x080aade8 in safe_free (ptr=0x40322620) at lib.c:127 Re: Jeffery von Ronne 2005-11-28 <[EMAIL PROTECTED]> > I've also been getting occasional IMAP related seg-faults. Re: Hilmar Preusse 2006-01-04 <[EMAIL PROTECTED]> > I believe I see the same bug here. The bug occurs, when I use my IMAP > INBOX. Re: Edward J. Shornock 2006-02-04 <[EMAIL PROTECTED]> > I had the segfault problem as well while using IMAP at the "Sorting > Folders" step. Upon downgrading to 1.5.11-5 the segfaults stopped. Re: Alan BRASLAU 2006-03-17 <[EMAIL PROTECTED]> > Systematic segmentation fault upon opening an imap mailbox. Hi, I'm just digging through Debian's mutt bug list. Can anyone of you still reproduce #277864 with recent mutt packages? At the moment 1.5.13-1.1 is in etch/sid and 1.5.14+cvs20070301-1 in experimental. It would be nice if you could give both a try and tell me which works/doesn't work. Thanks, Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Bug#277864: mutt segfault (imap)
Package: mutt Version: 1.5.11+cvs20060126-2 Followup-For: Bug #277864 Systematic segmentation fault upon opening an imap mailbox. Using the (stripped) unstable or testing mutt >gdb mutt run Looking up my-imap-server...(no debugging symbols found) Connecting to my-imap-server...(no debugging symbols found) (no debugging symbols found) ---Type to continue, or q to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Sorting mailbox... Program received signal SIGSEGV, Segmentation fault. 0xb7c4b598 in strncpy () from /lib/tls/libc.so.6 (gdb) bt #0 0xb7c4b598 in strncpy () from /lib/tls/libc.so.6 #1 0x080d8943 in ?? () #2 0x in ?? () No problem with my server/configuration using mutt/stable -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages mutt depends on: ii exim4 4.60-5 metapackage to ease exim MTA (v4) ii exim4-daemon-light [mail-tran 4.60-5 lightweight exim MTA (v4) daemon ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libdb4.3 4.3.29-5 Berkeley v4.3 Database Libraries [ ii libgnutls12 1.2.9-2the GNU TLS library - runtime libr ii libidn11 0.5.18-2 GNU libidn library, implementation ii libncursesw5 5.5-1 Shared libraries for terminal hand ii libsasl2 2.1.19-1.9 Authentication abstraction library Versions of packages mutt recommends: ii locales 2.3.6-3GNU C Library: National Language ( ii mime-support 3.36-1 MIME files 'mime.types' & 'mailcap -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
