On Thu, 2009 Aug 27 11:19+0200, Marco d'Itri wrote: > > This means that a malloc data structure is damaged. It may be caused > by BerkeleyDB.xs or not, probably not. To get *any* help you need to > provide useful information, start by running the program in valgrind > to have a chance of finding out what is corrupting the memory.
I have a debug-enabled libdb and libberkeleydb-perl ready to go here, but running all of Perl under Valgrind is too resource-intensive. Is there a way to limit Valgrind to the code in these libraries? > Are you aware that you need to arrange database locking by yourself? I believe apt-cacher is doing that correctly (see apt-cacher-lib-cs.pl). -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
