Jan Prunk wrote: > I would just like to say, that I cannot produce this bug on another > AMD_64 machine, where it works fine. The bug was produced on rented > VPS server, so it could be that VPS specific issue. I can select other > values fine there, like sort RES or SHR size. > > Here is the "valgrind htop" output, which you wanted: > > ==23679== at 0x4C9DA2E: strcmp (mc_replace_strmem.c:337) > ==23679== by 0x8058CA4: (within /usr/bin/htop) > ==23679== by 0x804E3E5: (within /usr/bin/htop) > ==23679== by 0x6D7D774: (below main) (in /lib/libc-2.9.so) > ==23679== Address 0x0 is not stack'd, malloc'd or (recently) free'd > htop 0.8.1 aborted. Please report bug at http://htop.sf.net > ==23679== > ==23679== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 28 from 3) > ==23679== malloc/free: in use at exit: 169,774 bytes in 645 blocks. > ==23679== malloc/free: 3,703 allocs, 3,058 frees, 1,548,535 bytes allocated. > ==23679== For counts of detected errors, rerun with: -v > ==23679== searching for pointers to 645 not-freed blocks. > ==23679== checked 250,980 bytes. > ==23679== > ==23679== LEAK SUMMARY: > ==23679== definitely lost: 156 bytes in 11 blocks. > ==23679== possibly lost: 0 bytes in 0 blocks. > ==23679== still reachable: 169,618 bytes in 634 blocks. > ==23679== suppressed: 0 bytes in 0 blocks. > ==23679== Rerun with --leak-check=full to see details of leaked memory. > > Kind regards, > Jan Prunk
Ok, so it's memory error. Will you mind If I ask you to rebuild the Debian package with debugging symbols included to see full gdb backtrace? This would require installing some additional development packages. If no, I will report this issue as is to author. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Maintainer
signature.asc
Description: OpenPGP digital signature
