Steve Langasek wrote: > Well, this problem indeed doesn't seem to be reproducible on i386 or amd64 > when not using nss_ldap. Given that users of other gnutls- or gcrypt-using > packages aren't reporting similar problems, it seems likely that this is a > bug in gaim-otr or libotr, but I don't think it's one that should block the > package from being released; it is generally usable, just not in certain > system configurations.
Yeah, I do have a system configuration that you don't run across every day ;-) Ian Goldberg wrote: > Is it reproducible on other systems that *do* use nss_ldap? Can you > turn nss_ldsp on on one of those other systems you tested, and try > again? I did a clean install of Debian unstable onto a x86 (32-bit) laptop, tested gaim with and without gaim-otr installed. gaim and gaim+otr both worked properly. Then I installed libnss-ldap and libpam-ldap and configured them for my network setup. gaim (without otr) worked, but gaim+otr had the same errors as I reported for my amd64 system (and the 32-bit chroot I also tested there). So I can duplicate the bug when nss_ldap is in use. Valgrind output is attached for the following 4 test cases: 1) gaim (without otr or nss_ldap): gaim.9110.gz 2) gaim+otr (without nss_ldap): gaim+otr.9180.gz 3) gaim with nss_ldap in use: gaim+ldap.10134.gz 4) gaim+otr with nss_ldap in use: gaim+otr+ldap.10038.gz Unfortunately, all of these valgrind runs on that x86 laptop have a TON of ===== Conditional jump or move depends on uninitialised value(s) at 0x5C55DC7: (within /usr/lib/libsoftokn3.so.0d) by 0x5C5617D: (within /usr/lib/libsoftokn3.so.0d) by 0x5C56243: (within /usr/lib/libsoftokn3.so.0d) by 0x5C56471: (within /usr/lib/libsoftokn3.so.0d) by 0x5C566D8: (within /usr/lib/libsoftokn3.so.0d) by 0x5C445C4: (within /usr/lib/libsoftokn3.so.0d) by 0x5C44721: (within /usr/lib/libsoftokn3.so.0d) by 0x5B9B7C2: (within /usr/lib/libnss3.so.0d) by 0x5B9B8C2: (within /usr/lib/libnss3.so.0d) by 0x5BA4133: SECMOD_LoadModule (in /usr/lib/libnss3.so.0d) by 0x5BA428A: SECMOD_LoadModule (in /usr/lib/libnss3.so.0d) by 0x5B8342D: (within /usr/lib/libnss3.so.0d) ===== that occur in each capture. I didn't see these on the amd64 system or the x86 chroot I set up on that system. Do you guys get pages and pages of that output when you run valgrind on gaim on a 32-bit x86 system? If not, I'll try to figure out what's causing it on that freshly installed laptop. - Michael
gaim.9110.gz
Description: application/gzip
gaim+otr.9180.gz
Description: application/gzip
gaim+ldap.10134.gz
Description: application/gzip
gaim+otr+ldap.10038.gz
Description: application/gzip
