![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| High Level Programming Post questions about C, C++, Java, SQL, and other programming languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Heap and stack | naan | High Level Programming | 5 | 04-30-2008 02:40 AM |
| Outside CEP: the infrastructure stack | iBot | Complex Event Processing RSS News | 0 | 12-14-2007 10:20 PM |
| memory stack | aladdin | UNIX for Dummies Questions & Answers | 1 | 05-16-2007 09:17 AM |
| stack region | yakari | UNIX for Advanced & Expert Users | 2 | 12-29-2006 09:34 AM |
| stack query | aloksave | High Level Programming | 4 | 09-16-2005 01:10 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
Sounds a little like homework. However:
When program run, each function(data, registers, program counter, etc) is mapped onto the stack as it is called. Because the function calls other functions, they too are mapped onto the stack. This is stack winding. Unwinding is the removal of the functions from the stack in the reverse order. |
|
||||
|
Where this starts getting fun is when you have exceptions or setjmp/longjmp which let you unwind the stack without returning.
Some platforms also have "structured exception handling" (OS/2,Win32) which are basically a standardised way of stack unwinding in exceptional conditions. Some platforms (eg 32bit PA-RISC) have a bottom-up stack rather than a top-down. |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|