Commit 76b0b8b
committed
Put report_error() back in a mutex
We may no longer need to wrap the ostream operations, but we still need
to wrap the test for whether report_error() is being called recursively.
Trying to just never call report_error() recursively would be doable for
the moment (the asserts inside `on_command_line` tests in `print_trace`
seem to be the only code path that can currently do it), but I don't see
a way to future proof that - we like to do lots of helpful things when
error reporting, and we like to fill the things we do with assertions.1 parent e262dde commit 76b0b8b
1 file changed
Lines changed: 6 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
390 | 390 | | |
391 | 391 | | |
392 | 392 | | |
| 393 | + | |
393 | 394 | | |
| 395 | + | |
394 | 396 | | |
395 | 397 | | |
396 | 398 | | |
| |||
418 | 420 | | |
419 | 421 | | |
420 | 422 | | |
| 423 | + | |
421 | 424 | | |
| 425 | + | |
422 | 426 | | |
423 | 427 | | |
424 | 428 | | |
| |||
428 | 432 | | |
429 | 433 | | |
430 | 434 | | |
| 435 | + | |
431 | 436 | | |
| 437 | + | |
432 | 438 | | |
433 | 439 | | |
434 | 440 | | |
| |||
0 commit comments