Machine-translated by Google. Questions are authored in English.
Top

Discussion

Sizing every task's stack from its measured high-water mark alone is risky because

  • A.the mark includes the kernel's own stack usage
  • B.the deepest path may not have been exercised in test
  • C.the mark is reset on every context switch
  • D.the kernel reports it in words rather than in bytes

Answer: B

An error path or an unusual input can add several frames that no test happened to reach, and the measurement says nothing about them. A margin over the measured worst case, plus static analysis of the call graph where it matters, is the safer practice.

No comment is present. Be the first to comment.
Loading…

Post your comment

Please log in or register to post a comment.