File tree Expand file tree Collapse file tree 1 file changed +4
-2
lines changed Expand file tree Collapse file tree 1 file changed +4
-2
lines changed Original file line number Diff line number Diff line change @@ -70,8 +70,10 @@ stack backtrace:
70
70
[ getting-a-backtrace-for-errors ] : #getting-a-backtrace-for-errors
71
71
72
72
If you want to get a backtrace to the point where the compiler emits
73
- an error message, you can pass the ` -Z treat-err-as-bug ` , which
74
- will make the compiler panic on the first error it sees.
73
+ an error message, you can pass the ` -Z treat-err-as-bug=n ` , which
74
+ will make the compiler skip ` n ` errors or ` delay_span_bug ` calls and then
75
+ panic on the next one. If you leave off ` =n ` , the compiler will assume ` 0 ` for
76
+ ` n ` and thus panic on the first error it encounters.
75
77
76
78
This can also help when debugging ` delay_span_bug ` calls - it will make
77
79
the first ` delay_span_bug ` call panic, which will give you a useful backtrace.
You can’t perform that action at this time.
0 commit comments