Page MenuHomePhabricator

Let the top-level exception handler dump a stack trace if we reach debug mode before things go sideways
ClosedPublic

Authored by epriestley on Feb 11 2019, 9:10 PM.
Tags
None
Referenced Files
F19105139: D20142.id.diff
Dec 5 2025, 8:39 PM
F19099513: D20142.diff
Dec 4 2025, 8:10 PM
F18867002: D20142.id.diff
Nov 3 2025, 8:53 PM
F18862671: D20142.diff
Nov 2 2025, 8:10 PM
F18857657: D20142.diff
Nov 1 2025, 4:59 PM
F18836422: D20142.diff
Oct 27 2025, 12:52 AM
F18817928: D20142.diff
Oct 21 2025, 7:32 PM
F18798491: D20142.id48103.diff
Oct 17 2025, 6:36 AM
Subscribers
None
Tokens
"100" token, awarded by joshuaspence.

Details

Summary

Depends on D20140. Ref T13250. Currently, the top-level exception handler doesn't dump stacks because we might not be in debug mode, and we might double-extra-super fatal if we call PhabricatorEnv:... to try to figure out if we're in debug mode or not.

We can get around this by setting a flag on the Sink once we're able to confirm that we're in debug mode. Then it's okay for the top-level error handler to show traces.

There's still some small possibility that showing a trace could make us double-super-fatal since we have to call a little more code, but AphrontStackTraceView is pretty conservative about what it does and 99% of the time this is a huge improvement.

Test Plan

Screen Shot 2019-02-11 at 1.00.45 PM.png (1×1 px, 350 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

amckinley added inline comments.
src/aphront/sink/AphrontHTTPSink.php
7–8

I just happened to notice this "do install" typo.

This revision is now accepted and ready to land.Feb 11 2019, 11:05 PM
  • Just remove that comment since we don't do either one, even though they're technically possible.
This revision was automatically updated to reflect the committed changes.