public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "f dot knauf at mmkf dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libmudflap/19319] Mudflap produce many violations on simple, correct c++ program Date: Thu, 07 May 2009 16:31:00 -0000 [thread overview] Message-ID: <20090507163057.17975.qmail@sourceware.org> (raw) In-Reply-To: <bug-19319-2476@http.gcc.gnu.org/bugzilla/> ------- Comment #34 from f dot knauf at mmkf dot de 2009-05-07 16:30 ------- I can confirm the behaviour for sparc-sun-solaris2.8, the first program mentioned in the last comment complains as follows: ******* mudflap violation 1 (check/write): time=1241712982.495997 ptr=ffbefac4 size=4 pc=ff288ac8 location=`/usr/local/lib/gcc/sparc-sun-solaris2.8/4.4.0/../../../../sparc-sun-solaris2.8/include/c++/4.4.0/bits/stl_tree.h:171:20 (std::_Rb_tree_iterator<std::pair<const int, int> >::_Rb_tree_iterator)' [0xff2876f0] Nearby object 1: checked region begins 1B after and ends 4B after mudflap object af548: name=`/usr/local/lib/gcc/sparc-sun-solaris2.8/4.4.0/../../../../sparc-sun-solaris2.8/include/c++/4.4.0/bits/stl_map.h:539:23 (std::map<int, int, std::less<int>, std::allocator<std::pair<const int, int> > >::insert) std::_Rb_tree_iterator<std::pair<const int, int> > __position' bounds=[ffbefac0,ffbefac3] size=4 area=stack check=1r/0w liveness=1 alloc time=1241712982.495900 pc=ff2881a4 Nearby object 2: checked region begins 4B before and ends 1B before mudflap object af440: name=`/usr/local/lib/gcc/sparc-sun-solaris2.8/4.4.0/../../../../sparc-sun-solaris2.8/include/c++/4.4.0/bits/stl_map.h:447:11 (std::map<int, int, std::less<int>, std::allocator<std::pair<const int, int> > >::operator[]) std::_Rb_tree_iterator<std::pair<const int, int> > __i' bounds=[ffbefac8,ffbefacb] size=4 area=stack check=0r/1w liveness=1 alloc time=1241712982.495875 pc=ff2881a4 Nearby object 3: checked region begins 4B before and ends 1B before mudflap dead object adc00: name=`/usr/local/lib/gcc/sparc-sun-solaris2.8/4.4.0/../../../../sparc-sun-solaris2.8/include/c++/4.4.0/bits/stl_map.h:447:11 (std::map<int, int, std::less<int>, std::allocator<std::pair<const int, int> > >::operator[]) std::_Rb_tree_iterator<std::pair<const int, int> > __i' bounds=[ffbefac8,ffbefacb] size=4 area=stack check=0r/1w liveness=1 alloc time=1241712982.495593 pc=ff2881a4 dealloc time=1241712982.495861 pc=ff287d58 number of nearby objects: 3 I compiled it with a gcc 4.4.0 cross compiler from i486-linux-gnu to sparc-sun-solaris2.8 (sparcv8), compiler options -fmudflap -lmudflap -lsocket (the last one being necessary to link mudflap). I had to remove the getmntent wrapper from the mudflap library because solaris 2.8 uses an interface different from the one gcc expects. Other than that, the gcc sources the compiler was built from were unchanged. As on x86, the same program compiled with the same options plus -m64 (i.e., for sparcv9) yields no mudflap errors. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19319
next prev parent reply other threads:[~2009-05-07 16:31 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19319-2476@http.gcc.gnu.org/bugzilla/> 2005-10-23 23:47 ` ppluzhnikov at charter dot net 2005-12-14 17:46 ` ppluzhnikov at charter dot net 2006-03-19 5:11 ` pinskia at gcc dot gnu dot org 2006-11-10 3:09 ` fche at redhat dot com 2006-11-10 16:34 ` p dot van-hoof at qub dot ac dot uk 2006-11-10 16:35 ` p dot van-hoof at qub dot ac dot uk 2006-11-10 23:00 ` ppluzhnikov at charter dot net 2006-11-10 23:31 ` ppluzhnikov at charter dot net 2006-11-14 3:53 ` fche at redhat dot com 2006-11-14 4:26 ` ppluzhnikov at charter dot net 2006-11-14 12:19 ` fche at redhat dot com 2006-11-15 1:22 ` ppluzhnikov at charter dot net 2007-06-10 19:32 ` awl03 at doc dot ic dot ac dot uk 2007-06-10 19:35 ` awl03 at doc dot ic dot ac dot uk 2007-06-20 19:37 ` fche at redhat dot com 2007-07-12 23:58 ` awl03 at doc dot ic dot ac dot uk 2007-08-27 18:41 ` jason at gcc dot gnu dot org 2008-04-09 19:15 ` fche at redhat dot com 2009-05-07 16:31 ` f dot knauf at mmkf dot de [this message] [not found] <bug-19319-4@http.gcc.gnu.org/bugzilla/> 2014-02-16 9:59 ` jackie.rosen at hushmail dot com 2005-01-07 22:31 [Bug libmudflap/19319] New: " bredelin at ucla dot edu 2005-01-07 22:42 ` [Bug libmudflap/19319] " fche at redhat dot com 2005-01-07 22:58 ` fche at redhat dot com 2005-01-08 20:03 ` bangerth at dealii dot org 2005-01-10 17:04 ` fche at redhat dot com 2005-01-18 9:35 ` bredelin at ucla dot edu 2005-02-13 18:35 ` cvs-commit at gcc dot gnu dot org 2005-02-13 20:08 ` cvs-commit at gcc dot gnu dot org 2005-02-13 20:09 ` fche at redhat dot com 2005-02-17 15:12 ` cvs-commit at gcc dot gnu dot org 2005-02-19 22:10 ` pinskia at gcc dot gnu dot org 2005-02-19 22:36 ` pinskia at gcc dot gnu dot org 2005-02-19 22:37 ` pinskia at gcc dot gnu dot org 2005-03-10 21:57 ` fche at redhat dot com 2005-04-20 2:36 ` pinskia at gcc dot gnu dot org 2005-08-18 20:05 ` gideon dot amos at canfieldsci dot com 2005-08-18 20:10 ` fche at redhat dot com 2005-08-18 22:36 ` pinskia at gcc dot gnu dot org 2005-09-23 21:35 ` cvs-commit at gcc dot gnu dot org 2005-09-23 21:35 ` fche at redhat dot com
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=20090507163057.17975.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).