Package: libnss-mdns
Version: 0.9-0.2
Severity: critical
Tags: security

I have two SPARC machines after  latest upgrade apt install avahi-package and
modify /etc/nsswitch.conf to use avahi. But now if I ping from one machine
to second ping crasehd with SIGBUS. If I ping from second to first ping not
crashed. Both machines runnig SID and are synced with repository.
There is back trace of this:
Core was generated by `ping e450'.
Program terminated with signal 10, Bus error.
#0  0xf7ef8b94 in _nss_mdns4_gethostbyaddr_r () from /lib/libnss_mdns4.so.2
(gdb) bt
#0  0xf7ef8b94 in _nss_mdns4_gethostbyaddr_r () from /lib/libnss_mdns4.so.2
#1  0xf7e682c4 in gethostbyaddr_r@@GLIBC_2.1.2 () from /lib/libc.so.6
#2  0xf7e68064 in gethostbyaddr () from /lib/libc.so.6
#3  0x00011140 in ?? ()
#4  0x00011140 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) 

Please look to bug 413471 I spend some time to solve may be similar problem.
This problem is only SPARC related and is caused by unaligned access to char
buffer.
When I stop avahi or modify /etc/nsswitch.conf to disable mdns4 and
mdns4_minimal ping not crash.
ssh,telnet,mysql crashed too but only when I ssh,mysql to machine from SPARC
machine and not crash when use i386.














-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: sparc (sparc64)

Kernel: Linux 2.6.20 (SMP w/1 CPU core)
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash

Versions of packages libnss-mdns depends on:
ii  avahi-daemon                  0.6.16-5   Avahi mDNS/DNS-SD daemon
ii  base-files                    4.0.0      Debian base system miscellaneous f
ii  libc6                         2.5-3      GNU C Library: Shared libraries
ii  perl                          5.8.8-7    Larry Wall's Practical Extraction 

libnss-mdns recommends no packages.

-- debconf-show failed


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to