From: | Frank Peters <frank.peters@×××××××.net> | ||
---|---|---|---|
To: | gentoo-amd64@l.g.o | ||
Subject: | Re: [gentoo-amd64] Request for verification - Chrome new window moved to other screens is black | ||
Date: | Fri, 26 Dec 2014 16:51:22 | ||
Message-Id: | 20141226115116.1d2d4b0cf7da75dd8b82ef7e@comcast.net | ||
In Reply to: | Re: [gentoo-amd64] Request for verification - Chrome new window moved to other screens is black by Frank Peters |
1 | On Fri, 26 Dec 2014 11:42:19 -0500 |
2 | Frank Peters <frank.peters@×××××××.net> wrote: |
3 | |
4 | > |
5 | > Are there command-line options to Chrome that would provide debugging |
6 | > output? |
7 | > |
8 | |
9 | After doing a quick check, I find that these switches may be helpful: |
10 | |
11 | Force logging to be enabled. Logging is disabled by default in release |
12 | builds. |
13 | --enable-logging |
14 | |
15 | Sets the minimum log level. Valid values are from 0 to 3: |
16 | INFO = 0, WARNING = 1, LOG_ERROR = 2, LOG_FATAL = 3. |
17 | --log-level |