GCC Bugzilla Bug 5694

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.

Release:
2.96

Environment:
Linux and I beleive any :-)

Hello,

well I'm sure that this would be nice, though there are plenty of other potentially dangerous 
functions. However at this point we certainly don't deal with this...

Dara

See Dara's comment:
other functions which gcc should warn about, sprintf, strcpy, and strcat.

The link-time warnings are in the domain of glibc, not GCC.

Jakub's patch <http://gcc.gnu.org/ml/gcc-patches/2004-09/msg02424.html>
provides for compile-time and runtime detection of some overflow cases,
and I think that is as much as is reasonable to go in GCC.  So once that
is in GCC, I think this bug should be closed.

(In reply to comment #3)
> Jakub's patch <http://gcc.gnu.org/ml/gcc-patches/2004-09/msg02424.html>
> provides for compile-time and runtime detection of some overflow cases,
> and I think that is as much as is reasonable to go in GCC.  So once that
> is in GCC, I think this bug should be closed.

Well it does not help other OS's other than glibc and newer glibc at that.