From: Rajeev Bansal <connectrajeev@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Warning for unsafe/insecure functions
Date: Sat, 1 Apr 2023 22:41:04 +0530 [thread overview]
Message-ID: <CAM05QofhDr=LUx6mdbKeHGcE02Er6Pv_ov=pUa5T86fKYtgWmA@mail.gmail.com> (raw)
In-Reply-To: <6dc16e33-647e-5bf5-4025-3e10141aaa66@jguk.org>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
Hi All,
I am looking for if gcc has the capability to report unsafe/insecure
functions used in a C Or CPP program? For example : if strcpy(), strcat(),
alloca(), atoi() etc. are used in a program then gcc should raise a
warning.
In my google search and gcc man page I couldn't find any gcc flags for this
purpose. Let's say if gcc doesn't have the inbuilt capability of reporting
of insecure function calls so how can I add this functionality in gcc?
Thanks,
-Rajeev
next prev parent reply other threads:[~2023-04-01 17:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 21:54 __attribute__ error ("message") Jonny Grant
2023-03-31 21:57 ` Jonathan Wakely
2023-03-31 21:58 ` Xi Ruoyao
2023-03-31 22:12 ` Jonny Grant
2023-03-31 22:13 ` Xi Ruoyao
2023-04-01 16:57 ` Jonny Grant
2023-04-01 23:00 ` Jonathan Wakely
2023-04-10 23:06 ` Jonny Grant
2023-04-01 17:11 ` Rajeev Bansal [this message]
2023-04-01 18:50 ` Warning for unsafe/insecure functions Xi Ruoyao
2023-04-02 2:12 ` Rajeev Bansal
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='CAM05QofhDr=LUx6mdbKeHGcE02Er6Pv_ov=pUa5T86fKYtgWmA@mail.gmail.com' \
--to=connectrajeev@gmail.com \
--cc=gcc-help@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).