Bug#922455: pinfo: malloc(): invalid size (unsorted)

[Jakub Wilk]

Package: pinfo
Version: 0.6.12-2
Severity: grave

pinfo doesn't start:

$ pinfo
Przemek's Info Viewer v0.6.12
malloc(): invalid size (unsorted)
Aborted

Valgrind suggests some memory corruption happened:

Syscall param stat64(file_name) points to unaddressable byte(s)
at 0x49FE605: __xstat64@@GLIBC_2.2 (xstat64.c:35)
by 0x10DCD3: stat (stat.h:455)
by 0x10DCD3: initpaths (filehandling_functions.c:1042)
by 0x10AAE8: main (pinfo.c:248)
Address 0x0 is not stack'd, malloc'd or (recently) free'd

Invalid write of size 4
at 0x10DE6A: initpaths (filehandling_functions.c:1051)
by 0x10AAE8: main (pinfo.c:248)
Address 0x4b008a8 is 0 bytes after a block of size 96 alloc'd
at 0x4836A16: calloc (in /usr/lib/i386-linux-gnu/valgrind/vgpreload_memcheck-x86-linux.so)
by 0x118C69: xmalloc (utils.c:110)
by 0x10DC7F: initpaths (filehandling_functions.c:1036)
by 0x10AAE8: main (pinfo.c:248)

Invalid write of size 4
at 0x10DE70: initpaths (filehandling_functions.c:1051)
by 0x10AAE8: main (pinfo.c:248)
Address 0x4b008ac is 4 bytes after a block of size 96 alloc'd
at 0x4836A16: calloc (in /usr/lib/i386-linux-gnu/valgrind/vgpreload_memcheck-x86-linux.so)
by 0x118C69: xmalloc (utils.c:110)
by 0x10DC7F: initpaths (filehandling_functions.c:1036)
by 0x10AAE8: main (pinfo.c:248)

...


-- System Information:
Architecture: i386

Versions of packages pinfo depends on:
ii libc6 2.28-7
ii libncursesw6 6.1+20181013-2
ii libreadline7 7.0-5
ii libtinfo6 6.1+20181013-2
ii install-info 6.5.0.dfsg.1-4+b1

[Debian Bug Tracking System]

Your message dated Sat, 16 Feb 2019 21:09:29 +0000
with message-id <E1gv7DF-00091I-***@fasolo.debian.org>
and subject line Bug#922455: fixed in pinfo 0.6.13-1
has caused the Debian Bug report #922455,
regarding pinfo: malloc(): invalid size (unsorted)
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 ***@bugs.debian.org
immediately.)