public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ahu at ds9a dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov/profile/26570] -fprofile-generate -fprofile-use cause memory corruption immediately Date: Sun, 05 Mar 2006 23:42:00 -0000 [thread overview] Message-ID: <20060305234227.15620.qmail@sourceware.org> (raw) In-Reply-To: <bug-26570-7094@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1684 bytes --] ------- Comment #3 from ahu at ds9a dot nl 2006-03-05 23:42 ------- Thanks Nicholas, I can run the command you suggest without errors (I saved the file as exploit.cc). However, if I compile first with -fprofile-generate, then run it once, and then add -fprofile-use, it reports: $ g++ -O2 -fprofile-use -fprofile-generate exploit.cc -o exploit *** glibc detected *** double free or corruption (fasttop): 0x085c7e78 *** exploit.cc: In function â_ForwardIterator2 std::swap_ranges(_ForwardIterator1, _ForwardIterator1, _ForwardIterator2) [with _ForwardIterator1 = int*, _ForwardIterator2 = int*]â: exploit.cc:14: internal compiler error: Aborted Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. This w/o any profiling information present: ahu@intel:~/work/pdns/pdns/pdns$ rm exploit.gc* ahu@intel:~/work/pdns/pdns/pdns$ g++ -O2 -fprofile-use -fprofile-generate exploit.cc -o exploit exploit.cc: In function âvoid std::iter_swap(_ForwardIterator1, _ForwardIterator2) [with _ForwardIterator1 = int*, _ForwardIterator2 = int*]â: exploit.cc:14: note: file exploit.gcda not found, execution counts estimated *** glibc detected *** double free or corruption (fasttop): 0x085f2438 *** exploit.cc: In function â_ForwardIterator2 std::swap_ranges(_ForwardIterator1, _ForwardIterator1, _ForwardIterator2) [with _ForwardIterator1 = int*, _ForwardIterator2 = int*]â: exploit.cc:14: internal compiler error: Aborted Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26570
next prev parent reply other threads:[~2006-03-05 23:42 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-05 23:26 [Bug tree-optimization/26570] New: " ahu at ds9a dot nl 2006-03-05 23:31 ` [Bug tree-optimization/26570] " nmiell at comcast dot net 2006-03-05 23:39 ` [Bug gcov/profile/26570] " pinskia at gcc dot gnu dot org 2006-03-05 23:42 ` ahu at ds9a dot nl [this message] 2006-03-05 23:53 ` pinskia at gcc dot gnu dot org 2006-03-05 23:56 ` pinskia at gcc dot gnu dot org 2006-03-06 0:02 ` [Bug gcov/profile/26570] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-03-06 0:04 ` pinskia at gcc dot gnu dot org 2006-03-06 0:10 ` ahu at ds9a dot nl 2006-04-16 18:42 ` mmitchel at gcc dot gnu dot org 2006-05-25 2:40 ` mmitchel at gcc dot gnu dot org 2006-08-07 12:08 ` hubicka at gcc dot gnu dot org 2006-08-12 8:20 ` rakdver at gcc dot gnu dot org 2006-08-16 7:06 ` patchapp at dberlin dot org 2006-08-17 2:03 ` [Bug gcov/profile/26570] [4.1 " pinskia at gcc dot gnu dot org 2006-10-18 9:24 ` [Bug gcov-profile/26570] " rguenth at gcc dot gnu dot org
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=20060305234227.15620.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).