crash_collector: pedantically document hashed string for warn_collector
When computing a hash of a kernel warning message, we include the trailing newline character. Document this fact, to make it easier to write separate tools that compute the hash. BUG=none TEST=cros_workon_make --board=link --test --reconf crash-reporter Change-Id: I5d78235db5c8bff7e3639c9d1cd3915d343f471e Reviewed-on: https://gerrit.chromium.org/gerrit/60797 Commit-Queue: mukesh agrawal <quiche@chromium.org> Reviewed-by: mukesh agrawal <quiche@chromium.org> Tested-by: mukesh agrawal <quiche@chromium.org>
This commit is contained in:
parent
4c9f576605
commit
32f827f9dd
1 changed files with 3 additions and 1 deletions
|
|
@ -48,7 +48,9 @@ END_TRACE {PREFIX}" ---[ end trace".*
|
|||
|
||||
^{CUT_HERE}\n{WARNING} BEGIN(PRE_WARN);
|
||||
.|\n /* ignore all other input in state 0 */
|
||||
<PRE_WARN>[^ ]+.[^ ]+\n if (WarnStart()) { /* yytext is file:line func+offset/offset() */
|
||||
<PRE_WARN>[^ ]+.[^ ]+\n if (WarnStart()) {
|
||||
/* yytext is
|
||||
"file:line func+offset/offset()\n" */
|
||||
BEGIN(WARN); ECHO;
|
||||
} else {
|
||||
BEGIN(0);
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue