public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/32984] add checking for array new & delete
Date: Mon, 06 Aug 2007 16:06:00 -0000	[thread overview]
Message-ID: <20070806160636.12203.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32984-9596@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from dcb314 at hotmail dot com  2007-08-06 16:06 -------
(In reply to comment #6)
> This is one which you need huge dataflow analysis 

Doubtful. Yes/No/Don't know flag on each pointer data
member of a class would be some of it.

> and whole program to detect this problem.

I'd be happy with a one file solution to this problem, as I hope
my original problem report made clear.

In summary, my customer doesn't have HP kit, valgrind is run time 
and not compile time, the compiler isn't going to be fixed anytime soon
so I feel a Perl script may be invented.

> So closing as won't fix.

Fair enough. Point taken. I'll try a Perl script.


-- 


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


  parent reply	other threads:[~2007-08-06 16:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-04 12:21 [Bug c++/32984] New: " dcb314 at hotmail dot com
2007-08-04 13:01 ` [Bug c++/32984] " gdr at cs dot tamu dot edu
2007-08-04 13:01 ` [Bug c++/32984] New: " Gabriel Dos Reis
2007-08-04 19:52 ` [Bug c++/32984] " dcb314 at hotmail dot com
2007-08-04 22:06   ` Gabriel Dos Reis
2007-08-04 22:06 ` gdr at cs dot tamu dot edu
2007-08-04 22:10 ` gdr at cs dot tamu dot edu
2007-08-05  0:31 ` sebor at roguewave dot com
2007-08-05 19:37 ` pinskia at gcc dot gnu dot org
2007-08-06 16:06 ` dcb314 at hotmail dot com [this message]
2007-08-09  2:54 ` fang at csl dot cornell dot edu
2007-08-09 16:03 ` dcb314 at hotmail 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=20070806160636.12203.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).