public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59598] very simple code using file open for read
Date: Sat, 28 Dec 2013 23:25:00 -0000	[thread overview]
Message-ID: <bug-59598-4-tv7MpPhu5J@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59598-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59598

Kai Tietz <ktietz at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #32 from Kai Tietz <ktietz at gcc dot gnu.org> ---
(In reply to Denis Kolesnik from comment #29)
> My code style has nothing to do with it. I even do not tell, that I do not
> fully like the interface of this site!!

Well, you coding-style and ability is poor.  Believe me. I wasn't referring to
those none-used arrays.

Think about this if-line in your second sample.  It contains the out of bounds
access:

...
        if((character_number >= word_begin_position[word_number]) &&
(character_number <= word_begin_position[word_number+1]) )
...

What is word_begin_position[word_number+1]???  Imagine you are within the final
word in your file.  The value at this position isn't initialized and therefore
contains random number.
Btw here in this line is also one of the logical failures you made.  Why your
if-condition includes first character of next word?

So you mights see, or I fear you won't, that your program has more then one bug
and therefore this is a invalid bug-report of gcc.


  parent reply	other threads:[~2013-12-28 23:25 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-25 16:56 [Bug c++/59598] New: " lirex.software at gmail dot com
2013-12-25 16:57 ` [Bug c++/59598] " lirex.software at gmail dot com
2013-12-25 16:59 ` lirex.software at gmail dot com
2013-12-25 17:08 ` pinskia at gcc dot gnu.org
2013-12-25 17:12 ` Denis.V.Kolesnik@safe-mail.net
2013-12-26 19:51 ` Denis.V.Kolesnik@safe-mail.net
2013-12-26 19:57 ` Denis.V.Kolesnik@safe-mail.net
2013-12-26 19:58 ` Denis.V.Kolesnik@safe-mail.net
2013-12-26 19:58 ` Denis.V.Kolesnik@safe-mail.net
2013-12-26 19:59 ` Denis.V.Kolesnik@safe-mail.net
2013-12-26 20:11 ` Denis.V.Kolesnik@safe-mail.net
2013-12-26 20:32 ` pinskia at gcc dot gnu.org
2013-12-26 20:34 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 15:07 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 17:01 ` schwab@linux-m68k.org
2013-12-28 17:18 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 19:31 ` pinskia at gcc dot gnu.org
2013-12-28 21:56 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 21:58 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 22:00 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 22:03 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 22:55 ` ktietz at gcc dot gnu.org
2013-12-28 22:59 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 23:01 ` ktietz at gcc dot gnu.org
2013-12-28 23:02 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 23:07 ` ktietz at gcc dot gnu.org
2013-12-28 23:12 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 23:13 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 23:17 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 23:18 ` Denis.V.Kolesnik@safe-mail.net
2013-12-28 23:25 ` ktietz at gcc dot gnu.org [this message]
2013-12-29 12:59 ` Denis.V.Kolesnik@safe-mail.net
2014-01-28 17:45 ` Denis.V.Kolesnik@safe-mail.net
2014-02-03 15:27 ` Denis.V.Kolesnik@safe-mail.net
2014-02-04  8:27 ` redi at gcc dot gnu.org
2014-02-08 17:02 ` Denis.V.Kolesnik@safe-mail.net
2014-02-08 17:05 ` Denis.V.Kolesnik@safe-mail.net
2014-02-08 17:19 ` Denis.V.Kolesnik@safe-mail.net
2014-02-08 17:46 ` schwab@linux-m68k.org
2014-02-08 18:09 ` Denis.V.Kolesnik@safe-mail.net
2014-02-08 18:09 ` Denis.V.Kolesnik@safe-mail.net
2014-02-08 18:11 ` Denis.V.Kolesnik@safe-mail.net
2014-02-08 18:59 ` redi at gcc dot gnu.org
2014-02-09 13:20 ` Denis.V.Kolesnik@safe-mail.net
2014-02-09 13:28 ` Denis.V.Kolesnik@safe-mail.net
2014-02-09 13:35 ` Denis.V.Kolesnik@safe-mail.net
2014-02-09 13:36 ` Denis.V.Kolesnik@safe-mail.net
2014-02-09 13:37 ` Denis.V.Kolesnik@safe-mail.net
2014-02-09 13:38 ` Denis.V.Kolesnik@safe-mail.net
2014-02-10 22:36 ` Denis.V.Kolesnik@safe-mail.net
2014-02-10 22:48 ` pinskia at gcc dot gnu.org
2014-02-10 23:12 ` Denis.V.Kolesnik@safe-mail.net
2014-02-10 23:14 ` Denis.V.Kolesnik@safe-mail.net
2014-02-10 23:30 ` pinskia at gcc dot gnu.org
2014-02-26 19:51 ` Denis.V.Kolesnik@safe-mail.net
2014-02-26 20:38 ` [Bug spam/59598] " redi at gcc dot gnu.org
2014-02-28  0:56 ` Denis.V.Kolesnik@safe-mail.net
2014-02-28  1:24 ` pinskia 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-59598-4-tv7MpPhu5J@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: link
Be 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).