Created
December 9, 2015 02:21
-
-
Save anish/f323f089312a9073dd17 to your computer and use it in GitHub Desktop.
valgrind sysdig
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sh-4.1# valgrind sysdig | |
==6934== Memcheck, a memory error detector | |
==6934== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. | |
==6934== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info | |
==6934== Command: sysdig | |
==6934== | |
==6934== Invalid read of size 1 | |
==6934== at 0x4A08180: strncpy (mc_replace_strmem.c:476) | |
==6934== by 0x602B8B: scap_create_userlist (in /usr/bin/sysdig) | |
==6934== by 0x5F5CAA: scap_open_live_int (in /usr/bin/sysdig) | |
==6934== by 0x5F65FC: scap_open (in /usr/bin/sysdig) | |
==6934== by 0x5DE952: sinsp::open(unsigned int) (in /usr/bin/sysdig) | |
==6934== by 0x5DEAA2: sinsp::open(std::string) (in /usr/bin/sysdig) | |
==6934== by 0x534C7C: sysdig_init(int, char**) (in /usr/bin/sysdig) | |
==6934== by 0x535B58: main (in /usr/bin/sysdig) | |
==6934== Address 0x0 is not stack'd, malloc'd or (recently) free'd | |
==6934== | |
==6934== | |
==6934== Process terminating with default action of signal 11 (SIGSEGV) | |
==6934== Access not within mapped region at address 0x0 | |
==6934== at 0x4A08180: strncpy (mc_replace_strmem.c:476) | |
==6934== by 0x602B8B: scap_create_userlist (in /usr/bin/sysdig) | |
==6934== by 0x5F5CAA: scap_open_live_int (in /usr/bin/sysdig) | |
==6934== by 0x5F65FC: scap_open (in /usr/bin/sysdig) | |
==6934== by 0x5DE952: sinsp::open(unsigned int) (in /usr/bin/sysdig) | |
==6934== by 0x5DEAA2: sinsp::open(std::string) (in /usr/bin/sysdig) | |
==6934== by 0x534C7C: sysdig_init(int, char**) (in /usr/bin/sysdig) | |
==6934== by 0x535B58: main (in /usr/bin/sysdig) | |
==6934== If you believe this happened as a result of a stack | |
==6934== overflow in your program's main thread (unlikely but | |
==6934== possible), you can try to increase the size of the | |
==6934== main thread stack using the --main-stacksize= flag. | |
==6934== The main thread stack size used in this run was 10485760. | |
==6934== | |
==6934== HEAP SUMMARY: | |
==6934== in use at exit: 2,063,859 bytes in 148 blocks | |
==6934== total heap usage: 9,294 allocs, 9,146 frees, 19,303,141 bytes allocated | |
==6934== | |
==6934== LEAK SUMMARY: | |
==6934== definitely lost: 5,940 bytes in 2 blocks | |
==6934== indirectly lost: 240 bytes in 10 blocks | |
==6934== possibly lost: 1,241 bytes in 38 blocks | |
==6934== still reachable: 2,056,438 bytes in 98 blocks | |
==6934== suppressed: 0 bytes in 0 blocks | |
==6934== Rerun with --leak-check=full to see details of leaked memory | |
==6934== | |
==6934== For counts of detected and suppressed errors, rerun with: -v | |
==6934== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 6 from 6) | |
Segmentation fault (core dumped) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment