diff options
author | Florian Bruhin <me@the-compiler.org> | 2019-06-20 16:36:17 +0200 |
---|---|---|
committer | Florian Bruhin <me@the-compiler.org> | 2019-06-20 16:36:17 +0200 |
commit | 3cbe1157814e22bf878860acea86235933c6b38f (patch) | |
tree | ebebc3ecd7230f70e0ce2a58aec13be7091b24d5 /qutebrowser/qutebrowser.py | |
parent | 093fe765fa68481215ad6e69b5c4d4f306a86e14 (diff) | |
download | qutebrowser-3cbe1157814e22bf878860acea86235933c6b38f.tar.gz qutebrowser-3cbe1157814e22bf878860acea86235933c6b38f.zip |
Add --debug-flag stack
Qt 5.12.3 disabled renderer process stack traces (by setting OFFICIAL_BUILD).
Comments in Chromium's source say that printing the stack trace has "security
implications", though it's unclear what those implications are precisely.
On older Qt versions, pass --disable-in-process-stack-traces for the same
effect. In newer Qt versions, pass --enable-in-process-stack-traces when
"--debug-flag stack" is given to re-enable them.
Diffstat (limited to 'qutebrowser/qutebrowser.py')
-rw-r--r-- | qutebrowser/qutebrowser.py | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/qutebrowser/qutebrowser.py b/qutebrowser/qutebrowser.py index 1efa8b9e4..c1894062f 100644 --- a/qutebrowser/qutebrowser.py +++ b/qutebrowser/qutebrowser.py @@ -165,9 +165,11 @@ def debug_flag_error(flag): no-sql-history: Don't store history items. no-scroll-filtering: Process all scrolling updates. log-requests: Log all network requests. + stack: Enable Chromium stack logging. """ valid_flags = ['debug-exit', 'pdb-postmortem', 'no-sql-history', - 'no-scroll-filtering', 'log-requests', 'lost-focusproxy'] + 'no-scroll-filtering', 'log-requests', 'lost-focusproxy', + 'stack'] if flag in valid_flags: return flag |