* László Böszörményi (GCS) <[email protected]>, 2015-04-28, 15:27:
It still crashes here.
According to AddressSantizer, it's a heap-based buffer overflow:
==8829==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf5a00753
at pc 0xf72c17b1 bp 0xfffc0b48 sp 0xfffc0b2c
WRITE of size 190 at 0xf5a00753 thread T0
#0 0xf72c17b0 in read (/usr/lib/i386-linux-gnu/libasan.so.1+0x237b0)
#1 0x8071c14 in read /usr/include/i386-linux-gnu/bits/unistd.h:44
[...]
Aha! I think I caught you. In the first bugreport you reported that
your system is amd64. Mine is amd64 as well and the segmentation fault
doesn't happen. It outputs a normal message about memory usage and exists.
But now in the backtrace your system seems to be i386.
Oops. I was using another machine for testing previously. But I've just
tried it on amd64, and it still crashes:
$ apt-cache policy lrzip
lrzip:
Installed: 0.621-1
Candidate: 0.621-1
Version table:
*** 0.621-1 0
500 http://ftp.debian.org/debian/ unstable/main amd64 Packages
100 /var/lib/dpkg/status
$ lrzcat crash.lrz > /dev/null
Warning, unable to set nice value
Decompressing...
How much memory your system has?
$ free -m
total used free shared buffers cached
Mem: 1980 1892 88 0 151 1243
-/+ buffers/cache: 497 1482
Swap: 0 0 0
--
Jakub Wilk
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
