Address Spaces & Layout

0 / 12 solved

Question Tags Difficulty Success

1. Address Space Layout

address_spacestack +3

Easy 70%

2. Two Ways To Share

threadsfork +2

Medium 57%

3. Two Pages Of Copying

copy-on-writefork +2

Medium 48%

4. Stack vs Heap Allocation Speed

Memory ManagementBasics

Medium 95%

5. Copy-on-Write

copy_on_writefork +2

Medium 79%

6. Costs Nothing On Disk

bssdata-segment +2

Medium 59%

7. Buffer Overflow

buffer_overflowstack +2

Medium 73%

8. Fourteen Thousand Frames Deep

stack-framesrecursion-depth +2

Medium 52%

9. Kernel vs User Address Space

kernel_spaceuser_space +2

Medium 55%

10. Better Save Space

bssdata-segment +2

Medium 73%

11. The Buffer That Worked In Testing

stack-framesdangling-pointer +2

Medium 73%

12. Where The Four Megabytes Went

address-space-layoutproc-maps +2

Hard 41%

address_spacestackheaplayoutmemorythreadsforkaddress-spacecopy-on-writepage-faultvirtual-memoryMemory ManagementBasicscopy_on_writevm_optimizationosbssdata-segmentstatic-storageexecutable-layoutbuffer_overflowsecuritystack-framesrecursion-depthaddress-space-layoutstack-overflowkernel_spaceuser_spacevirtual_address_spacelinkingelfdangling-pointerobject-lifetimeapi-designproc-mapsmallocmmap+1+2+3+4+5

Learning Resources

Operating Systems: Three Easy Pieces, Chapter 2, 13

Up next

12 of 12 questions here are still unsolved.

Next module Virtual Memory & Paging