From: Eli Zaretskii <eliz@gnu.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: about the usage of sprintf in gdb, specifically in gdb/remote.c
Date: Thu, 26 May 2005 03:47:00 -0000 [thread overview]
Message-ID: <usm0ay7ph.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0505260226350.22654@plinuxt18.cn.ibm.com> (message from Wu Zhou on Thu, 26 May 2005 02:37:08 -0700 (PDT))
> Date: Thu, 26 May 2005 02:37:08 -0700 (PDT)
> From: Wu Zhou <woodzltc@cn.ibm.com>
> cc: gdb@sources.redhat.com, gdb-patches@sources.redhat.com,
> mark.kettenis@xs4all.nl
>
> BTW, what is your point on my analysis in section 3.1. I believe
> it might incur an overflow.
I think so too.
> But I need to design a scenario to verify that.
That's my point exactly: you don't need to go to such lengths. If it
isn't 100% obvious that no overflow is possible, we should remove
sprintf in favor of safer functions.
next prev parent reply other threads:[~2005-05-26 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 13:00 Wu Zhou
2005-05-26 1:41 ` Eli Zaretskii
2005-05-26 3:11 ` Wu Zhou
2005-05-26 3:47 ` Eli Zaretskii [this message]
2005-05-26 6:37 ` Wu Zhou
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=usm0ay7ph.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=woodzltc@cn.ibm.com \
/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