Timeline for Structure of stack of a function call
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 29, 2016 at 19:58 | vote | accept | Torcellite | ||
| Jan 30, 2015 at 2:11 | comment | added | Torcellite | I've updated the question, sorry for the flurry of comments. | |
| Jan 30, 2015 at 1:39 | comment | added | Torcellite |
One more question, why is 48 bytes of space allocated to the stack in function? Please refer screenshot 2.
|
|
| Jan 30, 2015 at 1:19 | vote | accept | Torcellite | ||
| Feb 3, 2015 at 2:03 | |||||
| Jan 30, 2015 at 0:54 | comment | added | Torcellite |
Yep, I found out that the parameters and if all the variables of the function are uninitialized, they are not pushed onto the stack at all. However, the moment I initialized buffer1 as shown in my code, they all appeared. Is there any other circumstance when the callee function decides to push its members onto the stack?
|
|
| Jan 29, 2015 at 9:27 | history | edited | ysdx | CC BY-SA 3.0 |
added 118 characters in body
|
| Jan 29, 2015 at 9:12 | history | edited | ysdx | CC BY-SA 3.0 |
added 40 characters in body
|
| Jan 29, 2015 at 8:44 | history | edited | ysdx | CC BY-SA 3.0 |
added 548 characters in body
|
| Jan 29, 2015 at 8:23 | history | edited | ysdx | CC BY-SA 3.0 |
deleted 3 characters in body
|
| Jan 29, 2015 at 8:17 | history | edited | ysdx | CC BY-SA 3.0 |
deleted 3 characters in body
|
| Jan 29, 2015 at 8:12 | history | answered | ysdx | CC BY-SA 3.0 |