Please help crash: null byte in argument for long()
christocoleman at yahoo.com
Thu Apr 7 19:54:49 BST 2011
I agree Nicolas: it would be helpful to know which message the UID was referring
to. Possibly a dump of a "synthetic key": the unique idetifying information of
the message. (the subject/size/date/from/to, or the X-OfflineIMAP-xxxx field)
Maybe safer: the code can repair the damaged value. Input: the good UID. Using
this UID, the code retrieves the corresponding message, and uses a synthetic key
(the subject/size/date/from/to, or the X-OfflineIMAP-xxxx field) to match the
message, retrieve the missing UID and store it in the table.
From: Nicolas Sebrecht <nicolas.s-dev at laposte.net>
To: Sebastian Spaeth <Sebastian at SSpaeth.de>
Cc: chris coleman <christocoleman at yahoo.com>; offlineimap mailing list
<offlineimap-project at lists.alioth.debian.org>; Nicolas Sebrecht
<nicolas.s-dev at laposte.net>
Sent: Thu, April 7, 2011 2:33:35 PM
Subject: Re: Please help crash: null byte in argument for long()
On Thu, Apr 07, 2011 at 12:41:06AM +0200, Sebastian Spaeth wrote:
> On Wed, 6 Apr 2011 09:28:27 -0700 (PDT), chris coleman
><christocoleman at yahoo.com> wrote:
> > I unpacked v6.3.2 (not distro-specific), did chmod +x on the offlineimap.py,
> > ran it locally.
> > Same crash. "null byte in argument for long()"
> Thanks for the log and traceback. The crash you are seeing is because,
> you have a corrupt mapping file that translates the UIDS between the
> remote and the local IMAP servers.
So, it would be nice to prevent us to crash from that kind of
corruption. I think it worth implementing a warning or something if
internal data in general is corrupted.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OfflineIMAP-project