From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10962 invoked by alias); 10 Nov 2006 16:34:04 -0000 Received: (qmail 10454 invoked by uid 48); 10 Nov 2006 16:33:51 -0000 Date: Fri, 10 Nov 2006 16:34:00 -0000 Message-ID: <20061110163351.10453.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libmudflap/19319] Mudflap produce many violations on simple, correct c++ program In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "p dot van-hoof at qub dot ac dot uk" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-11/txt/msg00882.txt.bz2 List-Id: ------- Comment #19 from p dot van-hoof at qub dot ac dot uk 2006-11-10 16:33 ------- The reduced testcases listed previously in this thread indeed work correctly on the mainline, but a real C++ program that I tested still spewed thousands of violations, although valgrind could not find anything. The attached test case test.cc is one such example. Note that the test program tries to read its own source, so don't rename the file! > g++ -fmudflap test.cc -lmudflap > a.out ******* mudflap violation 1 (check/read): time=1163175853.725925 ptr=0x2ac0ae8ee720 size=8 pc=0x2ac0ae464871 location=`test.cc:18 (main)' /usr/local/gcc430/lib64/libmudflap.so.0(__mf_check+0x41) [0x2ac0ae464871] a.out(main+0x219) [0x40133d] /lib64/libc.so.6(__libc_start_main+0xf4) [0x2ac0aeb88154] number of nearby objects: 0 > g++ -v Using built-in specs. Target: x86_64-unknown-linux-gnu Configured with: /dump1/root/temp/gcc/configure --prefix=/usr/local/gcc430 --enable-languages=c,c++,fortran Thread model: posix gcc version 4.3.0 20061030 (experimental) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19319