Oleg, I haven't been able to reproduce these reliably. They do sometimes pop up during testing, but when I try to track them down they always point to lib/iniparser. I suspect there's some kind of contention over memory allocation between glibc's calloc and glib. Not sure though. Also very likely is some double-free somewhere.
A good way to track this down: set dbmail.conf to trace_level=5. trigger the error. grep the syslog for the actual commands and put them in a file cat file | valgrind --leak-check=full ./dbmail-imapd -n that should give a good indication where in the code this problem arises. Oleg wrote: >>Hello >> >>I run dbmail-svn (revision 1915) >> >>When I try to get mail from imapd, I get: >>*** glibc detected *** corrupted double-linked list: 0x080aa648 *** >> >>and can't read mail. >>With dbmail-2.0.7 - all OK >> >>What wrong I do ? > > > Can I help to resolve this situation? > > I wrote about this: > http://mailman.fastxs.net/pipermail/dbmail-dev/2005-October/007601.html > > and my results: > http://mailman.fastxs.net/pipermail/dbmail-dev/2005-October/007607.html > http://mailman.fastxs.net/pipermail/dbmail-dev/2005-October/007608.html > http://mailman.fastxs.net/pipermail/dbmail-dev/2005-October/007609.html > > I run dbmail-2.0.7 and have no glibc errors > But if I install dbmail-svn, I get error with the same database and client > > > -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
