From: "Martin Ettl" <ettl.martin@gmx.de>
To: Andrew Haley <aph@redhat.com>
Cc: java@gcc.gnu.org, ddaney@caviumnetworks.com
Subject: Re: found an overlapping data buffer in file natGCInfo.cc
Date: Tue, 28 Jul 2009 14:17:00 -0000 [thread overview]
Message-ID: <20090728141736.297030@gmx.net> (raw)
In-Reply-To: <4A6EB1DC.2000102@redhat.com>
-------- Original-Nachricht --------
> Datum: Tue, 28 Jul 2009 10:07:56 +0200
> Von: Andrew Haley <aph@redhat.com>
> An: Martin Ettl <ettl.martin@gmx.de>
> CC: ddaney@caviumnetworks.com, java@gcc.gnu.org
> Betreff: Re: found an overlapping data buffer in file natGCInfo.cc
> On 07/27/2009 09:09 PM, Martin Ettl wrote:
> > Hello friends,
> >
> > there are more bugs, not specially in the natGCInfo.cc but in e.g:
> libjava. I have no time to report all of them. I used cppcheck (an open source
> static code analysis tool) to find the bugs.
> > Here the output of the libjava scan with cppcheck:
> >
> >
> > Feel free to download and use cppcheck yourself.
>
> Are any of these actual bugs? I haven't checked every one, but those I
> have
> are style nag messages.
>
> Andrew.
I know, cppcheck brings a lots of stylistic warnings. These can be surpressed by not using the --style option. Then only memleaks, resource leaks and so on are shown.
The intention of my last message was to show you the possibilities of cppcheck, nothing more. I was not my intention to offend you, or your work. Gcc is a great tool, i am using it every day on serveral projects.... keep on guys!
Best regards
Martin
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
next prev parent reply other threads:[~2009-07-28 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 8:29 Martin Ettl
2009-07-27 10:03 ` Andrew Haley
2009-07-27 14:43 ` David Daney
2009-07-27 17:01 ` Andrew Haley
2009-07-27 19:09 ` Martin Ettl
2009-07-28 8:08 ` Andrew Haley
2009-07-28 14:17 ` Martin Ettl [this message]
2009-07-29 7:11 ` Andrew Haley
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=20090728141736.297030@gmx.net \
--to=ettl.martin@gmx.de \
--cc=aph@redhat.com \
--cc=ddaney@caviumnetworks.com \
--cc=java@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).