Your message dated Fri, 13 Apr 2012 22:56:00 +0100
with message-id
<CAPQ4b8nqMNh9PKNeT3eEyW3O9tsOY2BDVv=t6Wg=pg8jhce...@mail.gmail.com>
and subject line Closing obsolete/orphan bugs
has caused the Debian Bug report #247655,
regarding svnadmin crashes with "unaligned access"
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.)
--
247655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=247655
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: subversion
Version: 1.0.2-5
I want to run subversion on a parisc machine:
valinor:~# uname -a
Linux valinor.dawnlink.net 2.4.26-pa2 #1 Tue May 4 11:43:45 CEST 2004 parisc
GNU/Linux
When I try to create a repository, I get the following:
valinor:~# svnadmin create /d1/svn
svnadmin(12467): unaligned access to 0x4082be8c at
ip=0x401a55b7
Not-handled unaligned insn 0x0c6011d4
Unaligned handler failed, ret = -1
Bus error
I tried to reproduce that in gdb:
(gdb) run create /d1/svn
[...]
Program received signal SIGBUS, Bus error.
[Switching to Thread 16384 (LWP 12511)]
0x401a55b4 in __db_tas_mutex_lock_4002 () from
/usr/lib/libdb-4.2.so
(gdb) bt
#0 0x401a55b4 in __db_tas_mutex_lock_4002 () from /usr/lib/libdb-4.2.so
#1 0x4024dfdc in __memp_fget_4002 () from /usr/lib/libdb-4.2.so
#2 0x401b5e08 in __bam_search_4002 () from /usr/lib/libdb-4.2.so
#3 0x401abf28 in __bam_c_rget_4002 () from /usr/lib/libdb-4.2.so
#4 0x401aaddc in __bam_bulk_duplicates_4002 () from /usr/lib/libdb-4.2.so
#5 0x00000000 in ?? ()
--- End Message ---
--- Begin Message ---
Hello,
db4.2 has been removed many years ago and this bug report is orphan.
Sorry that the bug report was not dealt with when it was due, but I
guess that the issue was somehow fixed while the bug remained
unattended. Please reopen against current versions of libdb if there
are still issues.
Closing this bug report now.
--- End Message ---
