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]

[Bug other/28328] Stack smash protection non-verbose



------- Comment #6 from pinskia at gcc dot gnu dot org  2006-07-11 04:27 -------
(In reply to comment #4)
>   Thank you, I see the problem, there's a patch attached.  Your distribution
> should have a new version some time in a couple days.

Here is how normal GCC bugs go:
User (which is a developer, not neccessary of GCC): I ran some code through GCC
and GCC produced an internal compiler error.

Developer of GCC (if they did not follow the directions on the web page): Can
you attach the preprocessed source as mentioned on http://gcc.gnu.org/bugs.html

(if they did attach it, it is usually easy to figure out what is going on).

Really the developer should set up a correct way of reporting a bug, what they
require to report the bug.  Like your example, xmms instructions should be
like:
attach the sound file you were trying to play.
Everything else should fall out from there.  Now if developer's don't care
about their user that much, the user will move away from that program.  This is
called common sense about supply and demand.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28328


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