On Mon, Apr 18, 2011 at 08:16:57PM +0000, Antonio Radici wrote: > On Mon, Apr 18, 2011 at 05:41:12PM +0200, Nico Golde wrote: > > Hey Antonio, > > attached is the gdb backtrace. I anonymized some parts of it > > in order not to leak my mails and the imaps server I used, > > but this should not matter. > [...] > > If yes, this behaviour changed and mutt didn't try to decrypt mail bodies > > before in order to match these settings. > > Thanks Nico, > the backtrace was very helpful, I think we have a clear lead for the > resolution of this bug, I will get back to you as soon as possible.
Hi Nico, can you send me the entire color pattern you have? From what I see it seems that a pattern in the ColorIndexList list in the code is causing the call to msg_search() and consequentely mutt asks for a password. That shouldn't happen because the color patterns in that list should be only the one that start with: "color index" >From your list posted in the bug it doesn't seem that you have any 'color index' pattern, is that a full list of all your color directives? Another thing that can help is another run with the debugger, just re-do all the steps I wrote and at the point when you do 'bt' please jump the frame where the pattern is stored; if you take as an example your previous backtrace, pat=0x830380 is stored in frame 2 and 3, so I would do gdb) frame 3 gdb) print pat (in case you need to cast to the type, it is COLOR_LINE or 'struct color_line', but you shouldn't need to) If we cannot retrieve the pattern because we don't have any pattern in the conf or 'print pat' doesn't return anything useful, then another thing that you could do is going through the ColorIndexList and print all the patterns there: gdb) print ColorIndexList (you need to go through that list and print all the entities until 'next' is NULL) Let me know if you need any help. Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
