On Thu, Jun 13, 2013 at 11:00 PM, Nathan Hjelm <hje...@me.com> wrote: > ??? It looks like it is failing on pthread_create. That doesn't seem right. > Can you run under valgrind and see if anything obvious is wrong? I will test > in a Linux VM when I get home and see if I can reproduce the problem there.
Here are the results from valgrind. mcuee@Ubuntu1204VM:~/Desktop/build/libusbx/libusbx/build$ valgrind --tool=memcheck ./tests/stress ==9361== Memcheck, a memory error detector ==9361== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==9361== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==9361== Command: ./tests/stress ==9361== Starting test run: init_and_exit... Failed to init libusb on iteration 356: -99 Failure (1) Starting test run: get_device_list... Failed to init libusb: -99 Failure (1) Starting test run: many_device_lists... Failed to init libusb: -99 Failure (1) Starting test run: default_context_change... Failed to init libusb: -99 Failure (1) --- Ran 4 tests Passed 0 tests Failed 4 tests Error in 0 tests Skipped 0 tests ==9361== ==9361== HEAP SUMMARY: ==9361== in use at exit: 48,416 bytes in 356 blocks ==9361== total heap usage: 427,622 allocs, 427,266 frees, 71,841,938 bytes allocated ==9361== ==9361== LEAK SUMMARY: ==9361== definitely lost: 0 bytes in 0 blocks ==9361== indirectly lost: 0 bytes in 0 blocks ==9361== possibly lost: 48,416 bytes in 356 blocks ==9361== still reachable: 0 bytes in 0 blocks ==9361== suppressed: 0 bytes in 0 blocks ==9361== Rerun with --leak-check=full to see details of leaked memory ==9361== ==9361== For counts of detected and suppressed errors, rerun with: -v ==9361== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) mcuee@Ubuntu1204VM:~/Desktop/build/libusbx/libusbx/build$ valgrind --tool=memcheck --leak-check=yes ./tests/stress ==9722== Memcheck, a memory error detector ==9722== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==9722== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==9722== Command: ./tests/stress ==9722== Starting test run: init_and_exit... Failed to init libusb on iteration 356: -99 Failure (1) Starting test run: get_device_list... Failed to init libusb: -99 Failure (1) Starting test run: many_device_lists... Failed to init libusb: -99 Failure (1) Starting test run: default_context_change... Failed to init libusb: -99 Failure (1) --- Ran 4 tests Passed 0 tests Failed 4 tests Error in 0 tests Skipped 0 tests ==9722== ==9722== HEAP SUMMARY: ==9722== in use at exit: 48,416 bytes in 356 blocks ==9722== total heap usage: 427,622 allocs, 427,266 frees, 71,841,938 bytes allocated ==9722== ==9722== 48,416 bytes in 356 blocks are possibly lost in loss record 1 of 1 ==9722== at 0x402A5E6: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==9722== by 0x4011304: allocate_dtv (dl-tls.c:297) ==9722== by 0x4011AAB: _dl_allocate_tls (dl-tls.c:461) ==9722== by 0x406E470: pthread_create@@GLIBC_2.1 (allocatestack.c:571) ==9722== by 0x8054D07: linux_udev_start_event_monitor (linux_udev.c:98) ==9722== by 0x8053D14: op_init (linux_usbfs.c:454) ==9722== by 0x804B7F2: libusb_init (core.c:1789) ==9722== by 0x8049A7E: test_init_and_exit (stress.c:33) ==9722== by 0x804A07D: libusbx_testlib_run_tests (testlib.c:255) ==9722== by 0x80498C2: main (stress.c:158) ==9722== ==9722== LEAK SUMMARY: ==9722== definitely lost: 0 bytes in 0 blocks ==9722== indirectly lost: 0 bytes in 0 blocks ==9722== possibly lost: 48,416 bytes in 356 blocks ==9722== still reachable: 0 bytes in 0 blocks ==9722== suppressed: 0 bytes in 0 blocks ==9722== ==9722== For counts of detected and suppressed errors, rerun with: -v ==9722== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) -- Xiaofan ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
