public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "icegood1980 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55148] New: wrong compilation of chars: overlapped memory areas Date: Wed, 31 Oct 2012 12:10:00 -0000 [thread overview] Message-ID: <bug-55148-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55148 Bug #: 55148 Summary: wrong compilation of chars: overlapped memory areas Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: major Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: icegood1980@gmail.com if one uses a stringification operation then problems could be obtained on stack: brackets.cpp : #include <iostream> #include <cstring> #define GLOBAL_str_intermediate(s) \ ({ \ char GLOBAL_str_intermediate_buf[1024]; \ strcpy(GLOBAL_str_intermediate_buf, #s); \ GLOBAL_str_intermediate_buf[strlen(GLOBAL_str_intermediate_buf)-1]='\0'; \ GLOBAL_str_intermediate_buf+1; \ }) #define GLOBAL_str(s) GLOBAL_str_intermediate((s)) #define s_one_arg a,b,c int main(int argc, const char **argv) { char PairPotentialName[70], *p=GLOBAL_str(s_one_arg); // std::cerr<<p-PairPotentialName<<std::endl; std::cerr<<PairPotentialName+1<<std::endl; return 0; } g++ brackets.cpp ./a.out: 1 a,b,c so PairPotentialName and p are overlapped!
next reply other threads:[~2012-10-31 12:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-31 12:10 icegood1980 at gmail dot com [this message] 2012-10-31 12:17 ` [Bug c++/55148] " redi at gcc dot gnu.org 2012-10-31 12:23 ` redi at gcc dot gnu.org 2012-10-31 12:40 ` icegood1980 at gmail dot com 2012-10-31 12:43 ` icegood1980 at gmail 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=bug-55148-4@http.gcc.gnu.org/bugzilla/ \ --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).