Timeline for Can stack overflow be prevented by pushing return address first?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2018 at 15:48 | comment | added | Polynomial | @ioslearner To an extent, yes, but on x86 the stack is guaranteed to grow downwards. That's built into the architecture - it's a historical artefact from when the initial program counter would be set to 0, so it made sense to put the stack at the top of memory (e.g. 7FFF) and grow it down towards the rest of memory. ARM and SPARC have selectable stack growth directions, so you can reverse it to avoid this specific bug class somewhat. This doesn't fix other bug classes though, like write-what-where or heap corruption. | |
| Dec 14, 2018 at 2:02 | comment | added | ios learner | Hi @Polynomial, thanks for the detailed response. I think, basically, the real problem is that the stack grows downwards. If it grows upwards then all these problems will be solved? | |
| Dec 14, 2018 at 2:00 | vote | accept | ios learner | ||
| Dec 12, 2018 at 9:10 | history | answered | Polynomial | CC BY-SA 4.0 |