From: Mark Loeser <halcy0n@gentoo.org>
To: Tommy Vercetti <vercetti@zlew.org>
Cc: gcc@gcc.gnu.org
Subject: Re: c/c++ validator
Date: Sun, 19 Jun 2005 03:04:00 -0000 [thread overview]
Message-ID: <42B4E093.9050303@gentoo.org> (raw)
In-Reply-To: <200506190024.18033@gj-laptop>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
Tommy Vercetti wrote:
> Hi folks
>
> I would like to ask you about source validation software. Software that runs
> trough source code, and attempts to find any possible memory leaks, and other
> problems. Is there anything opensource for C or/and C++ out there ?
My summer research project that I'm working on is very closely related
to this. Its a static analysis tool that looks for problems like buffer
overflows, unitialized variables, and division by zero. Unfortunately
its not yet open sourced (probably because its still really really
beta), but I'm trying to talk to my advisor to see if he'd let me
continue working on it on my own and open source it, or if he is going
to release it at some point.
If you are interested, email me back off list and I'll talk to my advisor.
Mark Loeser
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-06-19 3:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 22:24 Tommy Vercetti
2005-06-18 22:32 ` Mathieu Malaterre
2005-06-18 22:38 ` Tommy Vercetti
2005-06-19 1:03 ` Gabriel Dos Reis
2005-06-19 1:44 ` Tommy Vercetti
2005-06-19 2:05 ` Gabriel Dos Reis
2005-06-19 2:16 ` Mathieu Malaterre
2005-06-19 2:48 ` Gabriel Dos Reis
2005-06-19 20:58 ` Tommy Vercetti
2005-06-20 19:53 ` Kai Henningsen
2005-06-20 20:58 ` Tommy Vercetti
2005-06-19 3:04 ` Mark Loeser [this message]
2005-06-19 2:41 Florian Krohm
2005-06-19 23:59 David Bremner
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=42B4E093.9050303@gentoo.org \
--to=halcy0n@gentoo.org \
--cc=gcc@gcc.gnu.org \
--cc=vercetti@zlew.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).