I just published "Stacktraces", the next piece in my "Understanding the Go Runtime" series, and it answers a question we all take for granted: how does the runtime know the entire call chain when your program panics?
The trace is built in two phases, and once you see them the
0
49
13
6.8K
Snapshot History (17)
| Date | ||||
|---|---|---|---|---|
| Jun 3 · 09:00 | 0 | +2 49 | +1 13 | +95 6.8K |
| Jun 3 · 08:00 | 0 | 47 | 12 | +124 6.7K |
| Jun 3 · 07:00 | 0 | 47 | 12 | +245 6.6K |
| Jun 3 · 04:00 | 0 | 47 | 12 | +140 6.3K |
| Jun 3 · 03:00 | 0 | +1 47 | +1 12 | +239 6.2K |
| Jun 3 · 00:00 | 0 | 46 | 11 | +95 6.0K |
| Jun 2 · 23:00 | 0 | 46 | +2 11 | +97 5.9K |
| Jun 2 · 22:00 | 0 | +1 46 | 9 | +139 5.8K |
| Jun 2 · 21:00 | 0 | +1 45 | 9 | +343 5.6K |
| Jun 2 · 18:00 | 0 | 44 | 9 | +174 5.3K |
| Jun 2 · 17:00 | 0 | +2 44 | 9 | +736 5.1K |
| Jun 2 · 15:00 | 0 | +1 42 | 9 | +208 4.4K |
| Jun 2 · 14:00 | 0 | 41 | 9 | +133 4.2K |
| Jun 2 · 13:00 | 0 | +1 41 | +1 9 | +148 4.0K |
| Jun 2 · 12:00 | 0 | +2 40 | 8 | +305 3.9K |
| Jun 2 · 10:00 | 0 | 38 | 8 | +127 3.6K |
| Jun 2 · 09:00 | 0 | +38 38 | +8 8 | +3.5K 3.5K |
| Jun 1 · 09:22 | 0 | 0 | 0 | 0 |