Source: curl
Version: 7.28.0-1
Severity: normal

I tried to build the package with the patch from #690551 but the build
just froze when it got to test 583. It said there was 10:24 remaining
after the previous successful test, but I'm pretty sure it had hung for
longer than that. It didn't seem to be using CPU etc.

debian/build/tests/log/upload583.txt is empty and I'll attach
debian/build/tests/log/valgrind583.

There were some other errors too, I don't know whether they're relevant:

test 582... valgrind ERROR 
 Leaked 24 bytes

 Leaked 24 bytes

Tests 111, 117, 118, 119, 122, 123, 144, 145, 190, 236, 290, 531, 533,
534, 546 were all marked "Killed". And:

test 165... valgrind ERROR 
 Read 4 invalid bytes

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
==14458== Memcheck, a memory error detector
==14458== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==14458== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==14458== Command: 
/home/tony/src/curl-7.28.0/debian/build/tests/libtest/.libs/lt-lib583 
sftp://localhost:8999/home/tony/src/curl-7.28.0/debian/build/tests/log/upload583.txt
 tony:
==14458== Parent PID: 14457
==14458== 
==14458== 
==14458== HEAP SUMMARY:
==14458==     in use at exit: 233,454 bytes in 4,104 blocks
==14458==   total heap usage: 6,280 allocs, 2,176 frees, 487,011 bytes allocated
==14458== 
==14458== 24 bytes in 1 blocks are definitely lost in loss record 536 of 662
==14458==    at 0x4C2A26B: malloc (vg_replace_malloc.c:270)
==14458==    by 0x7565960: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0)
==14458==    by 0x7566888: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0)
==14458==    by 0x7566BCE: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0)
==14458==    by 0x75AFA69: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0)
==14458==    by 0x56621E6: ??? (in /usr/lib/x86_64-linux-gnu/libssh2.so.1.0.1)
==14458==    by 0x566290A: ??? (in /usr/lib/x86_64-linux-gnu/libssh2.so.1.0.1)
==14458==    by 0x566A0A1: libssh2_session_handshake (in 
/usr/lib/x86_64-linux-gnu/libssh2.so.1.0.1)
==14458==    by 0x4E73C9B: ssh_statemach_act (ssh.c:722)
==14458==    by 0x4E77782: ssh_multi_statemach (ssh.c:2635)
==14458==    by 0x4E560C3: Curl_protocol_connect (url.c:3455)
==14458==    by 0x4E56399: Curl_setup_conn (url.c:5265)
==14458==    by 0x4E56443: Curl_connect (url.c:5338)
==14458==    by 0x4E6A344: multi_runsingle (multi.c:1150)
==14458==    by 0x4E6ADA4: curl_multi_perform (multi.c:1839)
==14458==    by 0x400F2F: test (lib583.c:63)
==14458== 
==14458== 24 bytes in 1 blocks are definitely lost in loss record 537 of 662
==14458==    at 0x4C2A26B: malloc (vg_replace_malloc.c:270)
==14458==    by 0x7565960: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0)
==14458==    by 0x7566888: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0)
==14458==    by 0x7566BCE: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0)
==14458==    by 0x75AFA69: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.11.7.0)
==14458==    by 0x56609B6: ??? (in /usr/lib/x86_64-linux-gnu/libssh2.so.1.0.1)
==14458==    by 0x5662196: ??? (in /usr/lib/x86_64-linux-gnu/libssh2.so.1.0.1)
==14458==    by 0x566290A: ??? (in /usr/lib/x86_64-linux-gnu/libssh2.so.1.0.1)
==14458==    by 0x566A0A1: libssh2_session_handshake (in 
/usr/lib/x86_64-linux-gnu/libssh2.so.1.0.1)
==14458==    by 0x4E73C9B: ssh_statemach_act (ssh.c:722)
==14458==    by 0x4E77782: ssh_multi_statemach (ssh.c:2635)
==14458==    by 0x4E560C3: Curl_protocol_connect (url.c:3455)
==14458==    by 0x4E56399: Curl_setup_conn (url.c:5265)
==14458==    by 0x4E56443: Curl_connect (url.c:5338)
==14458==    by 0x4E6A344: multi_runsingle (multi.c:1150)
==14458==    by 0x4E6ADA4: curl_multi_perform (multi.c:1839)
==14458== 
==14458== LEAK SUMMARY:
==14458==    definitely lost: 48 bytes in 2 blocks
==14458==    indirectly lost: 0 bytes in 0 blocks
==14458==      possibly lost: 0 bytes in 0 blocks
==14458==    still reachable: 233,406 bytes in 4,102 blocks
==14458==         suppressed: 0 bytes in 0 blocks
==14458== Reachable blocks (those to which a pointer was found) are not shown.
==14458== To see them, rerun with: --leak-check=full --show-reachable=yes
==14458== 
==14458== For counts of detected and suppressed errors, rerun with: -v
==14458== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 12 from 6)

Reply via email to