File: unsafe_buffers_paths.txt

package info (click to toggle)
chromium 139.0.7258.127-2
  • links: PTS, VCS
  • area: main
  • in suites: forky
  • size: 6,122,156 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (16 lines) | stat: -rw-r--r-- 645 bytes parent folder | download | duplicates (6) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
 
# Comment, then empty line with spaces.

.buffers,libc # diagnostics to enable.

  # indented comment then top-level file.
-unsafe_buffers_unchecked.cpp

-unsafe_buffers_not_clean_dir/ # Comment on same line
+unsafe_buffers_not_clean_dir/clean_header.h#Comment same line no space.
+unsafe_buffers_not_clean_dir/clean_dir_1/
-unsafe_buffers_not_clean_dir/clean_dir_1/still_not_clean_dir_3/

# Unnecessary exclusion of a directory that is already excluded.
# This shouldn't produce surprising behaviors, like including
# `unsafe_buffers_not_clean_dir_2/` again. See https://crbug.com/357649176
-unsafe_buffers_not_clean_dir/still_not_clean_dir_1/