Your message dated Wed, 20 Apr 2011 14:43:47 +0200
with message-id <[email protected]>
and subject line db4.6 moved to oldlibs
has caused the Debian Bug report #458134,
regarding db4.6-util: segfaults and othe rproblems
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.)
--
458134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=458134
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: db4.6-util
Version: 4.6.21-4
Severity: important
the db4.6-utils seem pretty hosed:
db4.6_dump segfaults:
db: Berkeley DB (Btree, version 9, native byte-order)
# db4.6_dump db
Segmentation fault
(backtrace shows some crash in __memp_resize but is otherwise useless)
db4.6_verify as well.
db4.6_stat -d db as well
db4.6_checkpoint -1 works fine
db4.6_printlog works fine
the database has been upgraded via db4.6_upgrade (which ran without
problems) and can be accessed/updated by programs linked against libdb4.6
seemingly without problems.
db4.6_stat -E gives:
db4.6_stat: DB_ENV->open: Cannot allocate memory
db4.6_stat: dbenv->close: Cannot allocate memory
[Exit 1]
strace:
open("DB_CONFIG", O_RDONLY) = -1 ENOENT (No such file or
directory)
stat("/var/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=232, ...}) = 0
open("__db.001", O_RDWR) = 3
fcntl(3, F_SETFD, FD_CLOEXEC) = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=24576, ...}) = 0
close(3) = 0
open("__db.001", O_RDWR) = 3
fcntl(3, F_SETFD, FD_CLOEXEC) = 0
mmap(NULL, 24576, PROT_READ|PROT_WRITE, MAP_SHARED, 3, 0) = 0x2b3f838c8000
close(3) = 0
write(2, "db4.6_stat: ", 12db4.6_stat: ) = 12
write(2, "DB_ENV->open", 12DB_ENV->open) = 12
write(2, ": ", 2: ) = 2
write(2, "Cannot allocate memory", 22Cannot allocate memory) = 22
write(2, "\n", 1
) = 1
write(2, "db4.6_stat: dbenv->close: Cannot"..., 49db4.6_stat: dbenv->close:
Cannot allocate memory
) = 49
exit_group(1) = ?
in short, 4.6 seems to be pretty hosed, the same app has worked fine with
db4.5 and db4.4 (the app still works with 4.6, but the utilities don't).
also, the database files are not portable among architectures (a database
file created on an x86 host will not work on an amd64 host, unlike the
claims in the documentation).
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.21-2-amd64
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages db4.6-util depends on:
hi libc6 2.7-5 GNU C Library: Shared libraries
ii libdb4.6 4.6.21-4 Berkeley v4.6 Database Libraries [
db4.6-util recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
since db4.6 no longer provides build environment and is kept only for
db upgrade purposes, and we never got a test case, I'm closing this
bug now. If you are able to provide us with a test case with version
in squeeze and/or db5.1 in unstable, then please reopen the bug
attaching a test case.
Thank you,
O.
--
Ondřej Surý <[email protected]>
--- End Message ---
