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

[nigelenki at comcast dot net]

------- Comment #4 from nigelenki at comcast dot net  2006-07-11 03:09 -------
(In reply to comment #3)
> If an end user gets a stack smash failure, they should report the bug to the
> developer and have the developer fix it.
> This is what is normally done for anyother bug, why should it be different than
> a stack smashing one?
> 

Because, like any normal report, it will go something like this:

END USER:

  xmms crashed

DEVELOPER:

  I need more info.

END USER:

  it crashed what do u mean

DEVELOPER:

  Why did it crash?

END USER:

  i unno it just did it was playin mp3s n it died

DEVELOPER:

  Did a specific MP3 cause it to crash?

END USER:

  maybe i cant make it do it agan tho i dunno y

DEVELOPER:

  Huh.  Meh.  I'll figure it out some time next year.



I would ultimately rather the report go like this:

END USER:

  xmms crashed

DEVELOPER:

  OK, can you see why?  First you should check 'dmesg | grep stack smash | grep
xmms'

END USER:

  ** stack smashing detected ***: mpg123_decode.c:decode_spline() (damage:
0xdeadbeef) Terminated

DEVELOPER:

  Thank you, I see the problem, there's a patch attached.  Your distribution
should have a new version some time in a couple days.


-- 


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