On Friday 08 April 2005 21:31, I wrote: > At last! That's the first time a problem wasn't due to my stupidity :o)
Which doesn't mean it'd go on like that - here is the first correction. The jumping-around-problem: silly me. I still had instruction reordering active in gcc. Switching it off got rid of the jumping and the strangely disappearing linked list - but did not change anything in the backtrace. Single stepping led me deep into gmime, but we already new that the crash happens there :-[ Continuing on a spare copy of my database, I tried removing the offending mails by hand: use strace to find out the message id that's causing the crash, delete the corresponding messageblks and let dbmail-util repair the damage (that's somewhat braindead, seriously messed up my cache, but did work out after all). The results: - after removing all offending mails inside a folder, KMail will no longer hang - dbmail-util will continue caching physmessages until the next bad message is encountered (then crash again). The success is persistent. - quite often gmime will spew a warning: "gmime-WARNING **: Invalid or incomplete type: : defaulting to application/octet-stream". This does not stop the processing > > is it some specific message that's crashing dbmail-util? That's a definite yes. Not only one but lots of them. The same messages obviously cause the hangs (inside dbmail-imapd, I guess) I can't say yet what is different about these mails. Could you recommend an SQL command to get a complete email in readable form when given the physmessage id? I'm just not used to reading messageblks ;-) I have a certain feeling that either during the migration to PostgreSQL 8 oder to dbmail-2.1.0 I seriously messed up the DB. Thank god for backups. -- With best regards, Florian Weber
