I researched sources and my results:
file: dbmail-message.c
function: dbmail_message_free
if I comment block:
// if (self->content)
// g_object_unref(self->content);
then, glibc error disappear and I can read mail.
I know, this is dirty hack, but it works...
Also, I modifi
One more test.
If I put command (for example):
4 UID FETCH 39567,39570 (UID RFC822.SIZE FLAGS ENVELOPE
BODY.PEEK[HEADER.FIELDS (REFERENCES)])
I get glibc error.
But, if I put command:
4 UID FETCH 39567,39570 (UID RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS
(REFERENCES)])
all OK !
So, getting
ELECT completed
4 UID FETCH 39567,39570 (UID RFC822.SIZE FLAGS ENVELOPE
BODY.PEEK[HEADER.FIELDS (REFERENCES)])
* 1105 FETCH (RFC822.SIZE 5080 FLAGS (\Seen \Answered \Recent) UID 39567
ENVELOPE ("Tue, 18 Oct 2005 09:24:43 +0200" "Re: [Dbmail-dev] One more bug
with dbmail-2.1
Paul J Stevens wrote:
> Oleg wrote:
> > Hello
> >
> > I run dbmail-2.1.3-svn with nearly 3500 messages in IMAP folders.
> > When I tried to read INBOX with 1108 messages, I get:
> >
> >
> > *** glibc detected *** corrupted double-linked list: 0x080f94e0 ***
>
> Bugger me. I've been seeing those as
Oleg wrote:
> Hello
>
> I run dbmail-2.1.3-svn with nearly 3500 messages in IMAP folders.
> When I tried to read INBOX with 1108 messages, I get:
> *** glibc detected *** corrupted double-linked list: 0x080f94e0 ***
Bugger me. I've been seeing those as well. But I'm unable to reproduce
them r
Hello
I run dbmail-2.1.3-svn with nearly 3500 messages in IMAP folders.
When I tried to read INBOX with 1108 messages, I get:
Oct 18 08:33:36 fox dbmail/imap4d[29662]: RESPONSE: [* LIST () "/" "INBOX"^M ]
Oct 18 08:33:36 fox dbmail/imap4d[29662]: RESPONSE: [4 OK LIST completed^M ]
Oct 18 08:33:
