headers
Mutt | 1 Jun 09:11

[Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP

 Mutt regularly crashes for me. I am using an IMAP box (Microsoft IMAP
 server), in parallel also thunderbird is listening to auto-filter selected
 messages into IMAP folders. This happens:

 {{{
 ---Mutt: imap://neteler <at> ntmail/INBOX [Msgs:1126 New:169 30M]---(reverse-
 date-received/date)------(3%)---
 Sorting mailbox...
 ---Type <return> to continue, or q <return> to quit---
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 182894227392 (LWP 9617)]
 0x000000000047c3c9 in imap_cache_del (idata=0x6035d0, h=0x8aeba0) at
 message.c:919
 919       snprintf (id, sizeof (id), "%u-%u", idata->uid_validity,
 HEADER_DATA(h)->uid);
 (gdb) bt

 0x000000000047c3c9 in imap_cache_del (idata=0x6035d0, h=0x8aeba0) at
 message.c:919
 919       snprintf (id, sizeof (id), "%u-%u", idata->uid_validity,
 HEADER_DATA(h)->uid);
 (gdb) bt
 #0  0x000000000047c3c9 in imap_cache_del (idata=0x6035d0, h=0x8aeba0) at
 message.c:919
 #1  0x000000000047cd28 in imap_fetch_message (msg=0x8af110, ctx=0x5fe130,
 msgno=Variable "msgno" is not available.
 ) at message.c:539
 #2  0x000000000043bcaf in mx_open_message (ctx=0x5fe130, msgno=0) at
(Continue reading)

Permalink | Reply | 12 comments |
headers
Mutt | 1 Jun 09:36

Re: [Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP

Comment (by neteler):

 I run it again, and after less than one our it crashes with

 {{{
 -*-Mutt: imap://neteler <at> ntmail/INBOX [Msgs:1120 New:2 Old:153 Del:8 30M
 ]---(reverse-date-received/date)-
 Fetching message headers... 1740/1740
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 182894227392 (LWP 3480)]
 mx_update_context (ctx=0x7f5100, new_messages=9897728) at mx.c:1566
 1566          h->security = crypt_query (h->content);
 (gdb)

 (gdb) bt
 #0  mx_update_context (ctx=0x7f5100, new_messages=9897728) at mx.c:1566
 #1  0x000000000047d64f in imap_read_headers (idata=0x6035d0,
 msgbegin=9897728, msgend=1739)
     at message.c:338
 #2  0x000000000047aac2 in imap_open_mailbox (ctx=0x7f5100) at imap.c:748
 #3  0x000000000043a827 in mx_open_mailbox (path=0x7fbfffe780
 "imap://neteler <at> ntmail/grassuser",
     flags=0, pctx=Variable "pctx" is not available.
 ) at mx.c:697
 #4  0x000000000041d349 in mutt_index_menu () at curs_main.c:1124
 #5  0x0000000000432746 in main (argc=1, argv=0x7fbffff658) at main.c:985
 (gdb)
 }}}
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jun 13:38

Re: [Mutt] #2902: Segmentation fault with IMAP

#2902: Segmentation fault with IMAP

Comment (by neteler):

 ... and one more (last for today):

 {{{
 Connecting to ntmail...[Thread debugging using libthread_db enabled]
 [New Thread 182894227392 (LWP 7578)]
 Fetching message headers... 1120/1123
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 182894227392 (LWP 7578)]
 0x0000000000477cae in imap_cmd_step (idata=0x6035d0) at command.c:561
 561           if (h && h->active && h->index+1 == msgno)
 (gdb) bt
 #0  0x0000000000477cae in imap_cmd_step (idata=0x6035d0) at command.c:561
 #1  0x000000000047d380 in imap_read_headers (idata=0x6035d0,
 msgbegin=8313776, msgend=1122)
     at message.c:249
 #2  0x000000000047aac2 in imap_open_mailbox (ctx=0x5fe130) at imap.c:748
 #3  0x000000000043a827 in mx_open_mailbox (path=0x7fbffff450
 "imap://neteler <at> ntmail/INBOX", flags=0,
     pctx=Variable "pctx" is not available.
 ) at mx.c:697
 #4  0x000000000043272d in main (argc=1, argv=0x7fbffff658) at main.c:982
 (gdb)
 }}}

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2902#comment:2>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jun 14:06

[Mutt] #2903: check PGP signature in background

#2903: check PGP signature in background

 Mutt should have an option to be able to check the PGP signature in
 background, as retrieving the key often takes time. Once the signature is
 checked, the index line should automatically be updated. The pager could
 also be automatically updated, but in this case, Mutt should make sure
 that it doesn't cause scrolling (except when the top of the message is
 displayed).

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2903>
Permalink | Reply | 2 comments |
headers
Brendan Cully | 2 Jun 02:20
Gravatar

dev.mutt.org offline this weekend

Due to electrical work, I'm going to have to take down dev.mutt.org
(the BTS and Mercurial repositories) for the weekend. It should be
back on Monday at the latest...
Permalink | Reply | 0 comments |
headers
Mutt | 2 Jun 15:11

[Mutt] #2904: recursive pgp_check_traditional() will crash on complicated multipart messages

#2904: recursive pgp_check_traditional() will crash on complicated multipart
messages

 pgp_check_traditional() is implemented recursively, so deeply nested
 multipart messages will cause a stack overflow, which can be annoying on
 systems with limited stack space.

 Reproduce:

 $ bash mime.sh > crash
 $ mutt -F /dev/null -f crash -e 'set pgp_auto_decode'
 Segmentation fault

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2904>
Permalink | Reply | 1 comment |
headers
Kyle Wheeler | 4 Jun 02:48

Re: [PATCH, RFC] mouse tracking support

On Thursday, May 31 at 03:12 PM, quoth Vincent Lefevre:
>On 2007-05-31 06:39:45 -0600, Kyle Wheeler wrote:
>>> | $ printf "\033[?9h"		# turn X10 mouse reporting on
>>> | $ printf "\033[?1000h"	# turn mouse reporting on
>>> | $ printf "\033[?1000l"	# turn mouse reporting off
>>
>> ... should I try the first two before starting mutt?
>
>No, just click in the terminal: if mouse reporting is on, you should
>see output, e.g.
>
>vin:~> printf "\033[?1000h"
>vin:~>  N4#N4 56#56 20#20
>        ^^^^^^^^^^^^^^^^^ obtained by clicking (this is just output)

$ printf "\033[?1000h"
$ D)#D)

That's a left-click. Here's a right-click:

$ "E"#E"

If I do the X10 mouse reporting thing first:

$ printf "\033[?9h"
$  4)

And the right-click:

$ "R%
(Continue reading)

Permalink | Reply | 2 comments |
headers
Cameron Simpson | 4 Jun 05:32
Picon
Picon
Gravatar

Re: [PATCH, RFC] mouse tracking support

On 03Jun2007 18:48, Kyle Wheeler <kyle-mutt-dev <at> memoryhole.net> wrote:
| $ printf "\033[?1000h"
| $ D)#D)
| 
| That's a left-click. Here's a right-click:
| 
| $ "E"#E"
| 
| If I do the X10 mouse reporting thing first:
| 
| $ printf "\033[?9h"
| $  4)
| 
| And the right-click:
| 
| $ "R%
| 
| So, clicking is definitely doing *something*.

You might do better running "od -c", then clicking and pressing
<return>. It should give better decoding of the sequences.
--

-- 
Cameron Simpson <cs <at> zip.com.au> DoD#743
http://www.cskk.ezoshosting.com/cs/

ObPeeve: It's long been suspected Orc had the sex drive of two men. As that
  second man, I'm not happy about this...       - TonyQ
Permalink | Reply | 1 comment |
headers
Thomas Dickey | 4 Jun 12:15
Picon

Re: [PATCH, RFC] mouse tracking support

On Mon, 4 Jun 2007, Cameron Simpson wrote:

> You might do better running "od -c", then clicking and pressing
> <return>. It should give better decoding of the sequences.

vttest has a test-screen for xterm's mouse controls (and doesn't rely on
other libraries than libc).

 	http://invisible-island.net/vttest

--

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
Permalink | Reply | 0 comments |
headers
Mike Hunter | 4 Jun 22:40

http://www.mutt.org

Hey guys,

I'm not sure this is the best place for website changes, but I noticed
both of these pages refer to an apparently non-existant IRC server:

http://www.mutt.org/doc/manual.txt
http://www.mutt.org/doc/manual/manual-1.html

Mike
Permalink | Reply | 1 comment |

Gmane