Displaying 7 results from an estimated 7 matches for "parse_next_body_to_boundary".
2007 Oct 21
1
Problem with fts found against Dovecot hg; examples + trace attached
...t/2007-10-21/broken.tar.gz
I've also attached the *.in and *.out files that I think are related to this
IMAP conversation.
On a different IMAP conversation with the same "SEARCH takes forever" problem,
I attached a gdb to the running Dovecot and got this backtrace:
(gdb) bt
#0 parse_next_body_to_boundary (ctx=0x85746e8, block_r=0xbf92325c)
at message-parser.c:332
#1 0x080c1b7d in message_parser_parse_next_block (ctx=0x85746e8,
block_r=0xbf92325c) at message-parser.c:717
#2 0xb7f582c2 in fts_mailbox_search_next_nonblock (ctx=0x811c0c0,
mail=0x811d380, tryagain_r=0xbf9232bb) at fts...
2010 Sep 15
1
imap processing spinning on the CPU
...who is seeing this on a FreeBSD server (that person moved back to dovecot 1.2 which 'solved' the problem there).
I didn't notice anything in the list archive about this, but maybe I missed it.
(gdb) bt full
#0 0x9534c2a8 in memchr ()
No symbol table info available.
#1 0x001ef220 in parse_next_body_to_boundary ()
No symbol table info available.
#2 0x001f02a8 in message_parser_parse_next_block ()
No symbol table info available.
#3 0x0013c1cc in index_mail_cache_parse_continue ()
No symbol table info available.
#4 0x0015c634 in mbox_save_body ()
No symbol table info available.
#5 0x0015ca14 in mbox_sav...
2013 Nov 05
1
Message parser loops on certain messages (e.g. with a trailing CR character)
Hi,
dovecot's message parser enters an endless loop when fed with certain
multipart messages with stray CR characters.
parse_next_body_to_boundary() assumes the '\r' might be the beginning
of a boundary line, reducing the block size by one:
src/lib-mail/message-parser.c:
404 /* no linefeeds in this block. we can just skip it. */
405 ret = 0;
406 if (block_r->data[block_r->size-...
2010 Sep 17
1
fts_squat hanging on some messages
...5:26:50 -0700 (PDT)
Size: 11434
URL: <http://dovecot.org/pipermail/dovecot/attachments/20100917/fd660314/attachment-0002.mht>
-------------- next part --------------
(gdb) bt full
#0 0x00007ff667019002 in memchr () from /lib/libc.so.6
No symbol table info available.
#1 0x00007ff667332f48 in parse_next_body_to_boundary (ctx=0xcd0d70, block_r=0x7fff6dc020a0)
at message-parser.c:350
boundary = 0x0
data = 0xcd64e0 "\n<html><head><title>Sicher ist Sicher! Richten Sie jetzt Ihren Hotmail Junk-Mail Filter ein!</title></head><body style=\"margin:0px;\"&...
2008 Dec 10
2
assert with zlib and (maybe) fts
Hi,
I compressed a folder with the following script:
...
for i in *.*.*; do
file $i | grep bzip2 >/dev/null 2>&1
if [ $? -ne 0 ]; then
echo "Compress: $i"
cat "$i" | bzip2 -9 > ../tmp/$i
if [ $? -eq 0 ]; then
mv ../tmp/$i $i
fi
else
2010 Aug 10
1
Why p_strdup and other string functions uses loops instead strlen? (dovecot 2.0.rc4)
...:
samples % symbol name
28000 10.9764 p_strdup
8507 3.3349 safe_memset
7857 3.0801 .plt
7627 2.9899 buffer_write
6871 2.6935 parse_body_add_block
And after (about four times smaller samples, but shows everything):
samples % symbol name
9595 26.2625 parse_next_body_to_boundary
8247 22.5729 parse_body_add_block
772 2.1130 .plt
672 1.8393 buffer_write
658 1.8010 __i686.get_pc_thunk.bx
614 1.6806 safe_memset
586 1.6039 pool_alloconly_malloc
559 1.5300 p_strdup
533 1.4589 hash_table_insert_node
I wonder why You use loop...
2009 Jun 02
2
Panic with signal 6 core dump with revision 9116:9ae55b68cf61
...ta(stream = 0x00000001100cbd20, data_r =
0x0fffffffffffecc0, size_r = 0x0fffffffffffecc8, threshold = 1), line
361 in "istream.c"
message_parser_read_more(ctx = 0x00000001100cc118, block_r =
0x0fffffffffffecb0, full_r = 0x0fffffffffffeb84), line 118 in "message-
parser.c"
parse_next_body_to_boundary(ctx = 0x00000001100cc118, block_r =
0x0fffffffffffecb0), line 330 in "message-parser.c"
message_parser_parse_next_block(ctx = 0x00000001100cc118, block_r =
0x0fffffffffffecb0), line 768 in "message-parser.c"
message_parser_parse_body(ctx = 0x00000001100cc118, hdr_callback =...