From: marty <martinbarrowcliff@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: ulogd2 on valgrind
Date: Wed, 23 Nov 2011 09:57:31 -0500 [thread overview]
Message-ID: <4ECD09DB.2060808@gmail.com> (raw)
Ulogd2 was compiled from current Git using recent x86 toolchain.
# valgrind --leak-check=yes /usr/sbin/ulogd -d
==22245== Memcheck, a memory error detector
==22245== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==22245== Using Valgrind-3.8.0.SVN and LibVEX; rerun with -h for
copyright info
==22245== Command: /usr/sbin/ulogd -d
==22245==
==22245== Invalid read of size 4
==22245== at 0x804A012: create_stack (ulogd.c:536)
==22245== by 0x804C83D: config_parse_file (conffile.c:198)
==22245== by 0x804B4DC: main (ulogd.c:949)
==22245== Address 0x28 is not stack'd, malloc'd or (recently) free'd
==22245==
==22245==
==22245== Process terminating with default action of signal 11 (SIGSEGV)
==22245== Access not within mapped region at address 0x28
==22245== at 0x804A012: create_stack (ulogd.c:536)
==22245== by 0x804C83D: config_parse_file (conffile.c:198)
==22245== by 0x804B4DC: main (ulogd.c:949)
==22245== If you believe this happened as a result of a stack
==22245== overflow in your program's main thread (unlikely but
==22245== possible), you can try to increase the size of the
==22245== main thread stack using the --main-stacksize= flag.
==22245== The main thread stack size used in this run was 8388608.
==22245==
==22245== HEAP SUMMARY:
==22245== in use at exit: 15,888 bytes in 107 blocks
==22245== total heap usage: 129 allocs, 22 frees, 17,866 bytes allocated
==22245==
==22245== LEAK SUMMARY:
==22245== definitely lost: 0 bytes in 0 blocks
==22245== indirectly lost: 0 bytes in 0 blocks
==22245== possibly lost: 0 bytes in 0 blocks
==22245== still reachable: 15,888 bytes in 107 blocks
==22245== suppressed: 0 bytes in 0 blocks
==22245== Reachable blocks (those to which a pointer was found) are not
shown.
==22245== To see them, rerun with: --leak-check=full --show-reachable=yes
==22245==
==22245== For counts of detected and suppressed errors, rerun with: -v
==22245== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 103 from 11)
Segmentation fault
If additional tests are desired please ask.
Marty B.
next reply other threads:[~2011-11-23 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 14:57 marty [this message]
2011-11-25 21:47 ` ulogd2 on valgrind Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ECD09DB.2060808@gmail.com \
--to=martinbarrowcliff@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).