Your message dated Mon, 29 Feb 2016 00:05:40 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-openssl-devel] Bug#705513: libssl1.0.0: 1.0.1e-3
illop in the same function
has caused the Debian Bug report #705513,
regarding openssl 1.0.1e-2 throws SIGILL on Debian 7.0 sparc
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.)
--
705513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705513
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openssl
Version: 1.0.1e-2
Severity: important
Tags: upstream
Dear Maintainer,
openssl 1.0.1e-2 throws SIGKILL on Debian 7.0 sparc. This may be related
to Bug #2553 SIGKILL on sparc64 (linux/solaris) reported on openssl.org:
http://rt.openssl.org/Ticket/Display.html?id=2553
Locally compiled program debug info:
(gdb) run
Starting program: /usr/local/bin/bitcoind
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/sparc-linux-gnu/libthread_db.so.1".
Traceback (most recent call last):
File "/usr/lib/debug/usr/lib/sparc-linux-gnu/libstdc++.so.6.0.17-gdb.py",
line 62, in <module>
from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named libstdcxx.v6.printers
Program received signal SIGILL, Illegal instruction.
0xf7b7cfdc in _sparcv9_fmadd_probe () at sparccpuid.S:312
312 sparccpuid.S: No such file or directory.
(gdb) bt
#0 0xf7b7cfdc in _sparcv9_fmadd_probe () at sparccpuid.S:312
#1 0xf7b7cc54 in OPENSSL_cpuid_setup () at sparcv9cap.c:227
#2 0xf7b78458 in _init () at sparccpuid.S:402
#3 0xf7fd920c in ?? () from /lib/ld-linux.so.2
#4 0xf7fd920c in ?? () from /lib/ld-linux.so.2
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
This bug on sparc is also discussed at:
http://www.mail-archive.com/[email protected]/msg70396.html
Cheers,
Mitch Halmu
-- System Information:
Debian Release: 7.0
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500,
'testing'), (500, 'stable')
Architecture: sparc (sparc64)
Kernel: Linux 3.2.0-4-sparc64-smp (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages openssl depends on:
ii libc6 2.13-38
ii libssl1.0.0 1.0.1e-2
ii zlib1g 1:1.2.7.dfsg-13
openssl recommends no packages.
Versions of packages openssl suggests:
ii ca-certificates 20130119
-- no debconf information
# cat /proc/cpuinfo
cpu : TI UltraSparc IIIi (Jalapeno)
fpu : UltraSparc IIIi integrated FPU
pmu : ultra3i
prom : OBP 4.22.33 2007/06/18 12:45
type : sun4u
ncpus probed : 2
ncpus active : 2
D$ parity tl1 : 0
I$ parity tl1 : 0
cpucaps : flush,stbar,swap,muldiv,v9,ultra3,mul32,div32,v8plus,vis,vis2
Cpu0ClkTck : 000000004c4b4000
Cpu1ClkTck : 000000004c4b4000
MMU Type : Cheetah+
State:
CPU0: online
CPU1: online
# openssl version
OpenSSL 1.0.1e 11 Feb 2013
# dpkg -l|egrep 'libssl1|libcrypto'
ii libcrypto++9 5.6.1-6
sparc General purpose cryptographic library - shared library
ii libssl1.0.0:sparc 1.0.1e-2
sparc SSL shared libraries
ii libssl1.0.0-dbg:sparc 1.0.1e-2
sparc Symbol tables for libssl and libcrypto
# dpkg -l|egrep 'libssl-dev|openssl'
ii libssl-dev 1.0.1e-2
sparc SSL development libraries, header files and documentation
ii openssl 1.0.1e-2
sparc Secure Socket Layer (SSL) binary and related cryptographic tools
--- End Message ---
--- Begin Message ---
On Sun, Feb 28, 2016 at 11:02:06PM +0100, Sebastian Andrzej Siewior wrote:
> This is a 64bit unaligned access which leads to the SIGBUS.
>
> Kurt, can you please close this bug? The last part of the bug could be
> reassigned to src:pandas but then they already have #790925 so there are busy.
> The orignal reported never got back it also looks like a problem in bitcoind
> than openssl.
Closing it.
Kurt
--- End Message ---
