This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

c/5694: Generate warning message about using vsprintf()

From: greendeath at mail dot ru
To: gcc-gnats at gcc dot gnu dot org
Date: 15 Feb 2002 01:21:52 -0000
Subject: c/5694: Generate warning message about using vsprintf()
Reply-to: greendeath at mail dot ru


>Number:         5694
>Category:       c
>Synopsis:       Generate warning message about using vsprintf()
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 14 17:26:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Eugene Zelenko
>Release:        2.96
>Organization:
>Environment:
Linux and I beleive any :-)
>Description:
gcc during link time write warning about using gets() - it's dangerous and so on.

I propose to add vsprintf() ti list of dangerouse functions whick can cause stack problem. May be add "use vsnprintf() instead".

Possible this warning can come in compiling time.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]