From: Simon Marchi <simark@simark.ca>
To: "Pavel I. Kryukov" <kryukov@frtk.ru>, gdb-patches@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: Re: [PATCH] sim-utils.c: prevent buffer overflow.
Date: Sun, 01 Dec 2019 14:46:00 -0000 [thread overview]
Message-ID: <969988fa-470f-9013-9948-dfff11922067@simark.ca> (raw)
In-Reply-To: <CADip9gbhoNmoS358B4wsw1wbX7AjT+5qxw+7bRoZcowXGv7wsw@mail.gmail.com>
On 2019-11-30 5:53 p.m., Pavel I. Kryukov wrote:
Is the sim built in C++ like GDB? If so, maybe this function could return
an std::string, so there's no more concerns of allocating a static buffer
with sufficient space?
next prev parent reply other threads:[~2019-12-01 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 22:54 Pavel I. Kryukov
2019-12-01 14:46 ` Simon Marchi [this message]
2019-12-01 15:33 ` Павел Крюков
2021-01-15 5:18 ` Mike Frysinger
2019-12-02 10:09 ` Andrew Burgess
2019-12-02 12:00 ` Pavel I. Kryukov
2019-12-02 19:06 ` Pavel I. Kryukov
2019-12-02 21:20 ` Andrew Burgess
2019-12-03 9:47 ` Pavel I. Kryukov
2019-12-04 17:39 ` Tom Tromey
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=969988fa-470f-9013-9948-dfff11922067@simark.ca \
--to=simark@simark.ca \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=kryukov@frtk.ru \
/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).