Stack smashing is a somewhat loosely defined term that may point to various issues and can come from a variety of sources. Stack smashing can happen involuntarily – for example, when the developer introduced a bug that caused stack smashing – or maliciously – an attacker somehow trying to overflow or corrupt the stack of a program. As a user, when you learn about stack smashing, the damage is likely done already. It is relatively easy (as in ‘somewhat easy’) for a developer to make a mistake that introduces stack smashing. As a developer, one will likely discover this term even earlier, especially if one has introduced a bug into the code, which causes a smashed stack. Working as a quality assurance engineer, one will sooner or later run into the term stack smashing. Learn what stack smashing is upfront and what can be done about it! What Is Stack Smashing? If your application has a serious issue that causes stack smashing, you’re in for a ride. Every minute of production downtime will generally cost a company money.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |