search for: literal8

...= imap_search_args_build(cmd, args, charset, &sargs); (gdb) p args[0] $1 = {type = IMAP_ARG_ATOM, parent = 0x0, str_len = 3, _data = {str = 0x85e40f8 "ALL", literal_size = 140394744, list = {arr = {buffer = 0x85e40f8, element_size = 0}, v = 0x85e40f8, v_modifiable = 0x85e40f8}}, literal8 = 0} (gdb) p args[1] $2 = {type = IMAP_ARG_ATOM, parent = 0x0, str_len = 3, _data = {str = 0x85e4100 "NOT", literal_size = 140394752, list = {arr = {buffer = 0x85e4100, element_size = 0}, v = 0x85e4100, v_modifiable = 0x85e4100}}, literal8 = 0} (gdb) p args[2] $3 = {type = IMAP_ARG_A...

On 06.12.2016 09:32, Toni Mattila wrote: > Hi, > > On 05-Dec-16 20:28, Toni Mattila wrote: >> Panicing stopped when all index files where deleted. > > It happens again in same user account, so rebuilding indexes didn't > fix it. > > Here's bt full instead of just bt: > #0 0x001d4402 in __kernel_vsyscall () > No symbol table info available. > #1

...pe encoding of the data/part itself with the encoding of the IMAP literal. A literal 8 is nothing more than a series of OCTET's that *may* contain nulls, but not necessarily. i.e., in the above example the 40 octets of data are US-ASCII text, which is perfectly acceptable to send as a literal8. (Client rationale: If BINARY exists on the server, we don't bother to scan IMAP literal's for null data -- we just send them as literal8's. It's an optimization that I would hate to get rid of.) michael

...ound: importing a mbox file containing ~700 messages (20 MB). Our program splits MULTIAPPENDS into approx. 5MB chunks. We don't use literal+ in order to immediately catch errors. I can reproducibly produce the following error (2.2.2) when doing a MULTIAPPEND where every append is using literal8: [...340 messages appended in 7 previous APPEND commands...] C: 10 APPEND Test "16-Dec-2011 17:19:46 -0700" ~{3128} [...~30 APPENDed messages...] C: "18-Jan-2012 12:38:21 -0700" ~{2893} S: + OK [...2893 octets of data...] C: "18-Jan-2012 22:09:41 -0700" ~{6492} S: 1...

...DSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY MOVE] Logged in as user A01 LIST "" ~/Mail/Gesendet A01 BAD Error in IMAP command LIST: literal8 not allowed here A02 LIST "" "~/Mail/Gesendet" * LIST (\NoInferiors \UnMarked) "/" ~/Mail/Gesendet A02 OK List completed. A03 STATUS ~/Mail/Gesendet (MESSAGES UNSEEN RECENT) A03 BAD Error in IMAP command STATUS: literal8 not allowed here A04 STATUS "~/Mail/Gesende...

...he > binary and core in seperate mail. > > Cheers, > > Toni Thanks. I should've probably said until EOL. $5 = {type = IMAP_ARG_EOL, parent = 0x0, str_len = 0, _data = {str = 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}}, literal8 = 0} Aki

...gt;> >> Cheers, >> >> Toni > > Thanks. I should've probably said until EOL. > > $5 = {type = IMAP_ARG_EOL, parent = 0x0, str_len = 0, _data = {str = > 0x0, literal_size = 0, list = {arr = {buffer = 0x0, element_size = 0}, > v = 0x0, v_modifiable = 0x0}}, literal8 = 0} > > Aki I was able to repeat this bug, thank you for your report. Aki

...chO::S_CSTRING_LITERALS); - if (IDVal == ".literal4") - return ParseDirectiveSectionSwitch("__TEXT", "__literal4", - MCSectionMachO::S_4BYTE_LITERALS, - 4); - if (IDVal == ".literal8") - return ParseDirectiveSectionSwitch("__TEXT", "__literal8", - MCSectionMachO::S_8BYTE_LITERALS, - 8); - if (IDVal == ".literal16") - return ParseDirectiveSectionSwitch(...