On Wed, 16 Jun 2004, Roland Hill wrote: >* Andreas Aardal Hanssen <[EMAIL PROTECTED]> [15-06-04 10:45]: >> Then, try to catch the crash (it is a crash) with gdb, by attaching to >> bincimapd before the FETCH command is submitted, or by tracing the >> bincimapd process with strace. You'll find a link to ProtocolDumping on >> the http://www.lifewithbincimap.org/ site that will help you provide some >> more info. >Well attached is my 'dump' using ethereal as noted under ProtocolDumping. >This is my first time at doing this so I hope it is correct.
The dump suggests that something is wrong with message 181, although we need a gdb dump or an strace dump to find the cause of the crash. Please try the strace approach, and if you can, try providing a gdb backtrace of bincimapd at the point where it crashes. This will tell us what message causes Binc to fail, and probably also why :-). Andy -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something http://www.bincimap.org/ | than to do it poorly."
