public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/54180] a bug using strcat function - it depends on variable declare order, but it should not. Date: Fri, 10 Aug 2012 14:51:00 -0000 [thread overview] Message-ID: <bug-54180-4-G0PfIAcpb6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54180-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54180 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID --- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-08-10 14:51:15 UTC --- Your bug report is useless, you have not provided the information requested at http://gcc.gnu.org/bugs/ so it cannot be compiled or verified, and your description of the problem is hard to follow. The problem is that your array is too small for the data you write to the array. This has nothing to do with the order of declarations. You declare SQL1[150] then you call strcat(SQL1,"select id,' ', to_char(dt_date,'DD.MM.YYYY'),' ',int_from,' ','>',' ',int_to,' ',cur_amount,' ',(select str_comment from tbl_dic_payment_types where tbl_dic_payment_types.id=tbl_bills.int_type) as type,' ', (select case when int_type=1 then 'business' else 'personal' end from tbl_bills_entity_type where tbl_bills_entity_type.int_bill=tbl_bills.id) as test2 from tbl_bills "); That's more than 150 characters. Your program has a bug, not GCC.
next prev parent reply other threads:[~2012-08-10 14:51 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-05 15:03 [Bug c++/54180] New: " lirex.software at gmail dot com 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 [this message] 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-G0PfIAcpb6@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).