| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
llvm-svn: 308541
|
|
|
|
| |
llvm-svn: 308336
|
|
|
|
|
|
| |
of very input (seems to work much better)
llvm-svn: 308253
|
|
|
|
| |
llvm-svn: 308246
|
|
|
|
|
|
|
|
| |
This reverts commit 546e006a023cccd0fd32afd442ab992d3515d4b8.
Reverting until I can figure out llvm-symbolizer breakages on mac os.
llvm-svn: 308202
|
|
|
|
| |
llvm-svn: 308075
|
|
|
|
|
|
|
|
|
|
|
| |
With this change, libFuzzer will ignore any arguments after a sigil
argument, but it will preserve these arguments at the end of the
command line when launching subprocesses. Using this, its possible to
handle positional and single-dash arguments to the program under test
by discarding everything up to -ignore_remaining_args=1 in
LLVMFuzzerInitialize.
llvm-svn: 308069
|
|
|
|
| |
llvm-svn: 308061
|
|
|
|
| |
llvm-svn: 307981
|
|
|
|
| |
llvm-svn: 307980
|
|
|
|
| |
llvm-svn: 307977
|
|
|
|
| |
llvm-svn: 307973
|
|
|
|
|
|
| |
corpus
llvm-svn: 307875
|
|
|
|
|
|
| |
to replace elements in the corpus with smaller ones that have the same feature set. Still needs tuning
llvm-svn: 307873
|
|
|
|
| |
llvm-svn: 307862
|
|
|
|
|
|
| |
more
llvm-svn: 307858
|
|
|
|
| |
llvm-svn: 307857
|
|
|
|
|
|
|
|
|
| |
Some libFuzzer tests on Linux would fail with bizarre error messages
unless llvm-symbolizer binary is present.
Differential Revision: https://reviews.llvm.org/D35313
llvm-svn: 307826
|
|
|
|
|
|
|
|
|
|
|
| |
The current code relies on the assumption that tests are included only
if LLVM_USE_SANITIZE_COVERAGE is enabled.
This commit makes it easier to relax the assumption in the future, as
the variable LIBFUZZER_FLAGS_BASE is used further in libFuzzer tests.
Differential Revision: https://reviews.llvm.org/D35314
llvm-svn: 307825
|
|
|
|
|
|
| |
Differential Revision: https://reviews.llvm.org/D35312
llvm-svn: 307824
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
```
./FuzzerIOWindows.cpp:185:1: warning: multi-line comment [-Wcomment]
// Parse a directory ending in separator, like: SomeDir\
^
./FuzzerIOWindows.cpp:200:1: warning: multi-line comment [-Wcomment]
// Parse a servername and share, like: SomeServer\SomeShare\
^
```
Differential Revision: https://reviews.llvm.org/D35244
llvm-svn: 307687
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The warning is reproducible with GCC 4.8. Thanks to David Blaikie for
the suggested fix.
The reported warning was
```
/usr/local/google/home/echristo/sources/llvm/lib/Fuzzer/FuzzerExtFunctions.def:29:10: warning: ISO C++ forbids casting between pointer-to-function and pointer-to-object [-Wpedantic]
EXT_FUNC(__lsan_enable, void, (), false);
^
/usr/local/google/home/echristo/sources/llvm/lib/Fuzzer/FuzzerExtFunctionsWeak.cpp:44:24: note: in definition of macro ‘EXT_FUNC’
CheckFnPtr((void *)::NAME, #NAME, WARN);
^
```
Differential Revision: https://reviews.llvm.org/D35243
llvm-svn: 307686
|
|
|
|
|
|
|
|
| |
This fixes a bug where unmodifiable strings where passed to posix_spawn.
This is an attempt to unbreak the greendragon libFuzzer bot.
llvm-svn: 307424
|
|
|
|
|
|
| |
cases where libFuzzer is run w/o initial corpus or with a corpus of very small items.
llvm-svn: 305521
|
|
|
|
|
|
| |
On Darwin, section names have a 16char length limit.
llvm-svn: 305429
|
|
|
|
|
|
| |
currently)
llvm-svn: 305346
|
|
|
|
| |
llvm-svn: 305335
|
|
|
|
|
|
| |
libFuzzer. This is not fully functional yet, but simple tests work
llvm-svn: 305331
|
|
|
|
|
|
|
| |
dependencies and add comments to tell future maintainers about those
requirements.
llvm-svn: 304843
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I did this a long time ago with a janky python script, but now
clang-format has built-in support for this. I fed clang-format every
line with a #include and let it re-sort things according to the precise
LLVM rules for include ordering baked into clang-format these days.
I've reverted a number of files where the results of sorting includes
isn't healthy. Either places where we have legacy code relying on
particular include ordering (where possible, I'll fix these separately)
or where we have particular formatting around #include lines that
I didn't want to disturb in this patch.
This patch is *entirely* mechanical. If you get merge conflicts or
anything, just ignore the changes in this patch and run clang-format
over your #include lines in the files.
Sorry for any noise here, but it is important to keep these things
stable. I was seeing an increasing number of patches with irrelevant
re-ordering of #include lines because clang-format was used. This patch
at least isolates that churn, makes it easy to skip when resolving
conflicts, and gets us to a clean baseline (again).
llvm-svn: 304787
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reviewers: craig.topper, arsenm, mehdi_amini
Reviewed By: mehdi_amini
Subscribers: mehdi_amini, wdng, nhaehnle, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D33924
llvm-svn: 304767
|
|
|
|
| |
llvm-svn: 304333
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This allows to keep handlers installed by sanitizers.
In other cases third-party code can replace handlers after libFuzzer
initialization anyway.
Reviewers: kcc
Subscribers: llvm-commits
Differential Revision: https://reviews.llvm.org/D33522
llvm-svn: 303828
|
|
|
|
| |
llvm-svn: 303128
|
|
|
|
|
|
| |
individual inputs with afl driver
llvm-svn: 303125
|
|
|
|
|
|
| |
Christian Holler. This also fixes a logical bug, which however does not affect the libFuzzer's ability too much (I wasn't able to create a differentiating test)
llvm-svn: 303087
|
|
|
|
| |
llvm-svn: 302747
|
|
|
|
| |
llvm-svn: 302498
|
|
|
|
|
|
| |
(if it is -- report an error)
llvm-svn: 302494
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
It's not safe to assume that atexit handlers can be run once the app crashed.
Patch by Jochen Eisinger.
Reviewers: kcc, vitalybuka
Subscribers: llvm-commits
Differential Revision: https://reviews.llvm.org/D32640
llvm-svn: 302076
|
|
|
|
|
|
|
|
|
| |
This has been mysteriously failing since r301593, which cleaned up the
types of things like size_t and SIZE_MAX for freestanding targets. Reid
and Kostya suggested marking it as UNSUPPORTED on windows, given that no
one has been able to reproduce locally.
llvm-svn: 301719
|
|
|
|
|
|
| |
This shows up as a -Wpendatic error on GCC.
llvm-svn: 301616
|
|
|
|
| |
llvm-svn: 301061
|
|
|
|
|
|
| |
available.
llvm-svn: 301058
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two reasons why users might want to build libfuzzer:
- To fuzz LLVM itself
- To get the libFuzzer.a archive file, so that they can attach it to their code
This change always builds libfuzzer, and supports the second use case if the specified flag is set.
The point of this patch is to have something that can potentially be shipped with the compiler, and this also ensures that the version of libFuzzer is correct to use with that compiler.
Patch by George Karpenkov.
Differential Revision: https://reviews.llvm.org/D32096
llvm-svn: 301054
|
|
|
|
| |
llvm-svn: 301017
|
|
|
|
| |
llvm-svn: 301012
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two reasons why users might want to build libfuzzer:
- To fuzz LLVM itself
- To get the libFuzzer.a archive file, so that they can attach it to their code
This change always builds libfuzzer, and supports the second use case if the specified flag is set.
The point of this patch is to have something that can potentially be shipped with the compiler, and this also ensures that the version of libFuzzer is correct to use with that compiler.
Patch by George Karpenkov.
Differential Revision: https://reviews.llvm.org/D32096
llvm-svn: 301010
|
|
|
|
|
|
|
|
| |
Old Apple compilers do not support thread_local keyword. This patch adds -Dthread_local=__thread when the compiler doesn't support thread_local.
Differential Revision: https://reviews.llvm.org/D32312
llvm-svn: 301007
|
|
|
|
|
|
|
|
|
|
|
| |
Older compilers (e.g. LLVM 3.4) do not support the attribute target("popcnt").
In order to support those, this diff check the attribute support using the preprocessor.
Patch by George Karpenkov.
Differential Revision: https://reviews.llvm.org/D32311
llvm-svn: 300999
|