public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/40502] [4.5 Regression] crash in cp_diagnostic_starter
Date: Mon, 22 Jun 2009 05:34:00 -0000	[thread overview]
Message-ID: <20090622053432.7193.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40502-9596@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]



------- Comment #4 from pinskia at gcc dot gnu dot org  2009-06-22 05:34 -------
as witness from:
In function ‘char* strncpy(char*, const char*, size_t)’,
    inlined from ‘void pat_read_waveheader(FILE*, WaveHeader*, int)’ at
t.cc:7132:40:
t.cc:1965:94: warning: call to char* __builtin___strncpy_chk(char*, const
char*, long unsigned int, long unsigned int) will always overflow destination
buffer


If I add an obvious check for block being NULL.


-- 


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


  parent reply	other threads:[~2009-06-22  5:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20 12:33 [Bug c++/40502] New: " dcb314 at hotmail dot com
2009-06-20 12:34 ` [Bug c++/40502] " dcb314 at hotmail dot com
2009-06-20 13:07 ` [Bug middle-end/40502] [4.5 Regression] " rguenth at gcc dot gnu dot org
2009-06-22  5:33 ` pinskia at gcc dot gnu dot org
2009-06-22  5:34 ` pinskia at gcc dot gnu dot org [this message]
2009-06-27 20:07 ` reichelt at gcc dot gnu dot org
2009-07-09 15:42 ` rguenth at gcc dot gnu dot org
2009-07-10  8:18 ` jakub at gcc dot gnu dot org
2009-07-10 11:50 ` manu at gcc dot gnu dot org
2009-07-10 11:57 ` jakub at gcc dot gnu dot org
2009-07-10 22:32 ` jakub at gcc dot gnu dot org
2009-07-10 22:37 ` jakub 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=20090622053432.7193.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: 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).