Your message dated Wed, 20 Apr 2011 14:46:37 +0200
with message-id <[email protected]>
and subject line db4.6 is going away
has caused the Debian Bug report #510270,
regarding DB: Logging region out of memory; you may need to increase its size
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
510270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510270
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libdb4.6
Version: 4.6.21-11
When I built my application against libdb4.6-dev on amd64, after a
fairly short period of activity it failed with the following error from
libdb:
DB: Logging region out of memory; you may need to increase its size
I tried bumping the logging region to 512KB in environment setup, but
this did not fix the problem.
I tried db4.5 and db4.7 (the latter from unstable). As far as I can
tell neither of these provoke this behaviour (which is why I think this
is libdb's bug not mine). This is enough to solve my immediate problem
although building with non-default libdb in lenny is rather inconvenient
as other -dev packages appear to depend on the broken libdb4.6-dev.
I see from the upstream db4.7 changelog that there's some references to
fixing logging region leaks. I've not yet attempted to analyze whether
these changes are the actual cause but could possibly be persuaded to at
least experiment with them if there was a realistic possibility that
they would at some point be applied to lenny's db4.6 if suitably isolated.
ttfn/rjk
--- End Message ---
--- Begin Message ---
db4.6 is going to be kept only for old database upgrades, and it's no
longer linkable (it builds only libdb4.6 and db4.6-util now) and you
have stated that db4.7 solved your problem, I am closing this issue as
fixed in libdb4.7 and higher.
Thanks,
--
Ondřej Surý <[email protected]>
--- End Message ---
