[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#412569: zdump -v segmentation fault on alpha

Package: libc6.1
Version: 2.3.2.ds1-22sarge5
Severity: normal

*** Please type your report below this line ***
After glibc update, zdump -v segfault
alpha300:~# zdump -v /etc/localtime
Erreur de segmentation

As a notice, zdump --version does not work (same on x86)

Before the update, there was a different failure
alpha300:~# zdump --version
@(#)zdump.c 7.64
alpha300:~# zdump -v /etc/localtime
/etc/localtime -9223372036854775808 = NULL
/etc/localtime -9223372036854689408 = NULL

Then you had to stop the program with ctrl/C

After compilation of zdump from tzcode2007b.tar.gz with
make zdump

it show
alpha300:~# ./zdump --version
@(#)zdump.c     8.3
alpha300:~# ./zdump -v /etc/localtime
/etc/localtime  -9223372036854775808 = NULL
/etc/localtime  -9223372036854689408 = NULL

so the behavior is same as before the update and it does not work as

alpha300:~# cat /proc/cpuinfo
cpu                     : Alpha
cpu model               : EV45
cpu variation           : 7
cpu revision            : 0
cpu serial number       :
system type             : Avanti
system variation        : 0
system revision         : 0
system serial number    : AY
cycle frequency [Hz]    : 267895671 est.
timer frequency [Hz]    : 1024.00
page size [bytes]       : 8192
phys. address bits      : 34
max. addr. space #      : 63
BogoMIPS                : 529.40
kernel unaligned acc    : 0 (pc=0,va=0)
user unaligned acc      : 0 (pc=0,va=0)
platform string         : AlphaServer 300 4/266
cpus detected           : 1

this is my first report on debian, I find nothing for libc-2.3.2
I know #266438 for libc-2.2.5-11.2 and #266438 for libc-2.3.6.ds1

-- System Information:
Debian Release: 3.1
Architecture: alpha
Kernel: Linux 2.4.27-2-generic
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)

Versions of packages libc6.1 depends on:
ii  libdb1-compat                 2.1.3-7    The Berkeley database routines

-- no debconf information

Reply to: