public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lirex.software at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/54180] New: a bug using strcat function - it depends on variable declare order, but it should not. Date: Sun, 05 Aug 2012 15:03:00 -0000 [thread overview] Message-ID: <bug-54180-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54180 Bug #: 54180 Summary: a bug using strcat function - it depends on variable declare order, but it should not. Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: lirex.software@gmail.com Created attachment 27940 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27940 source file Hello, I want to report bugs: I using gcc gcc-4.6.1 on Microsoft Windows XP (service pack 3) the options of the compiler: c++ -I"D:\Program Files\PostgreSQL\9.1\include" -L"D:\Program Files\PostgreSQL\9.1\lib" -lpq -o %application_file% %application_file%.cpp -Wl,--subsystem,windows -lgdi32 -lcomctl32 -D_WIN32_IE=0x0300 the complete command line that triggers the bug: just a part of my code which handles a window key pressure the compiler output (error messages, warnings, etc.); and: it outputs not the value which is expected, but partially(!) the value of other variable: if it should display a date with SQL_date_begin it displays a part of SQL1 (I replaced almost everywhere the parrword needed to access my Postgre SQL database) the function strcat works only proper if I declare char variables as follow: CHAR SQL_date_begin[10], SQL_date_end[10],SQL1[150], SQL_result[100]; but no way if: CHAR SQL1[150], SQL_date_begin[10], SQL_date_end[10], SQL_result[100]; somewhy in second order it owerwrites value of SQL_date_begin note: to form the value of SQL_date_begin I use strcpy(SQL_date_begin,""); wsprintf(chBuffer,_T("%d"),date_time_begin.wYear); strcat(SQL_date_begin,chBuffer); strcat(SQL_date_begin,"-"); ...(only a part) Regards, Denis Kolesnik.
next reply other threads:[~2012-08-05 15:03 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-05 15:03 lirex.software at gmail dot com [this message] 2012-08-05 15:08 ` [Bug c++/54180] " lirex.software at gmail dot com 2012-08-05 15:11 ` lirex.software at gmail dot com 2012-08-05 15:12 ` schwab@linux-m68k.org 2012-08-05 15:13 ` lirex.software at gmail dot com 2012-08-09 23:19 ` lirex.software at gmail dot com 2012-08-09 23:22 ` pinskia at gcc dot gnu.org 2012-08-09 23:33 ` lirex.software at gmail dot com 2012-08-09 23:35 ` pinskia at gcc dot gnu.org 2012-08-10 14:16 ` lirex.software at gmail dot com 2012-08-10 14:51 ` redi at gcc dot gnu.org 2012-08-10 15:04 ` redi at gcc dot gnu.org 2012-08-16 22:26 ` schwab@linux-m68k.org 2012-08-16 22:35 ` lirex.software at gmail dot com 2012-08-16 23:00 ` pinskia at gcc dot gnu.org 2012-08-17 0:03 ` redi at gcc dot gnu.org 2012-08-18 21:16 ` lirex.software at gmail dot com 2012-08-18 21:29 ` lirex.software at gmail dot com 2012-08-18 22:07 ` lirex.software at gmail dot com 2012-08-18 22:12 ` lirex.software at gmail dot com 2012-08-18 22:19 ` redi at gcc dot gnu.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=bug-54180-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).