From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Emile Michel Hobo <e.m.hobo@hotmail.nl>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: strcpy and strcat seem to lead to a stack overflow
Date: Wed, 23 Feb 2022 09:47:12 +0000 [thread overview]
Message-ID: <CAH6eHdS9feX5FOh+nmOc6eMsmokQKHq=FYBLANpdJ9XRUnDmUg@mail.gmail.com> (raw)
In-Reply-To: <AM6P194MB0263B192623F4BBFD53A4C10AE3B9@AM6P194MB0263.EURP194.PROD.OUTLOOK.COM>
On Tue, 22 Feb 2022 at 21:02, Emile Michel Hobo wrote:
> I hope you can fix this.
There is nothing to fix, strcpy and strcat work exactly as required by
the C standard, and that isn't going to change. In any case, it's
off-topic on this mailing list because those functions are defined in
the C standard and provided by the C library on your OS, not by GCC.
This list is for discussing the development of GCC itself.
> Personally, I’m looking into switching to Ada.
GCC has a very capable Ada compiler, so maybe you will be happy using
that instead of C.
prev parent reply other threads:[~2022-02-23 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 21:01 Emile Michel Hobo
2022-02-23 0:47 ` Patrick McGehearty
2022-02-23 8:58 ` lego12239
2022-02-23 9:47 ` Jonathan Wakely [this message]
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='CAH6eHdS9feX5FOh+nmOc6eMsmokQKHq=FYBLANpdJ9XRUnDmUg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=e.m.hobo@hotmail.nl \
--cc=gcc@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).