The GCE metadata server can be unresponsive sometimes, resulting in this
exception.
This should address the root cause of the stack trace pointed out in
https://github.com/google/oss-fuzz/pull/11727
OSS Fuzz documentation says that default name of dictionary file is the
same as fuzzer filename:
> If the dict filename is the same as your target binary name
> (i.e. `%fuzz_target%.dict`), it will be automatically used.
The patch fixes `build.sh` accordingly.
This reverts commit d9a8b11259.
It should be safe to revert it now that
https://github.com/actions/runner-images/issues/9491 is closed.
That stopgap was also reverted in
ae0e1cb989
and the CI confirmed that other workflows with sanitizers are fine so
CIFuzz/CFLite should be fine as well.
This PR fixes a Coverage build failure reported in
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=67425.
The failure is due to missing Java 21 support in the coverage container
when running JaCoCo:
```
Caused by: java.lang.IllegalArgumentException: Unsupported class file major version 65
```
Unfortunately, I couldn't find a way to add Java 21 support. As a
workaround, I've downgraded the Java version to 17 when building the
project.
I've tested the changes locally and the Coverage build is now passing.
If you have an idea how to add Java 21 support instead of downgrading to
17, please let me know.
Related: https://github.com/google/oss-fuzz-gen/pull/172, #11700.
This simplifies the link generation in benchmark `JSON`.
Previously, the binary directory name matches the binary name, now it is
always called `target_binary/`.
MSAN recently broke on github actions. Add a command that works
around the issue to temporarily unbreak MSAN.
Remove this commit when the issue is fixed later this week.
Fixes: https://github.com/google/oss-fuzz/issues/11703
Helps https://github.com/google/oss-fuzz-gen/issues/156:
1. `target_experiment.py` takes a new parameter,
`upload_reproducer_path`.
2. `target_experiment.py` saves crash reproducer to
`local_artifect_path`.
3. `target_experiment.py` uploads the fuzz target binary and the crash
reproducer to bucket directory `upload_reproducer_path`.
Fix the mbedtls build in bignum-fuzzer and cryptofuzz. (mbedtls and
ecc-diff-fuzzer still had `--recursive` from earlier days.)
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
monorail keeps updating every open issue every other day and also keeps
sending notifications to everyone.
To judge from https://github.com/google/oss-fuzz/issues/6825 it happens
due to inactive addresses and the only way to fix it is to remove
addresses like that.
Instead, tar up the project directory ourselves, upload this to GCS, and
create the Build ourselves.
This is also a lot more efficient, as we're excluding a lot of
unnecessary dirs from being uploaded.
Fixes: https://github.com/google/oss-fuzz-gen/issues/163
Downgrades Rust to nightly at 28th Dec 2023. The version that is build
is:
```sh
> [2/2] RUN install_rust.sh:
0.210 + curl https://sh.rustup.rs
0.210 + sh -s -- -y --default-toolchain=nightly-2023-12-28 --profile=minimal
0.217 % Total % Received % Xferd Average Speed Time Time Time Current
0.217 Dload Upload Total Spent Left Speed
100 26495 100 26495 0 0 205k 0 --:--:-- --:--:-- --:--:-- 206k
0.348 info: downloading installer
1.603 warning: it looks like you have an existing installation of Rust at:
1.603 warning: /usr/local/bin
1.603 warning: It is recommended that rustup be the primary Rust installation.
1.603 warning: Otherwise you may have confusion unless you are careful with your PATH
1.603 warning: If you are sure that you want both rustup and your already installed Rust
1.603 warning: then please reply `y' or `yes' or set RUSTUP_INIT_SKIP_PATH_CHECK to yes
1.603 warning: or pass `-y' to ignore all ignorable checks.
1.603 error: cannot install while Rust is installed
1.603 warning: continuing (because the -y flag is set and the error is ignorable)
1.622 info: profile set to 'minimal'
1.622 info: default host triple is x86_64-unknown-linux-gnu
1.622 info: syncing channel updates for 'nightly-2023-12-28-x86_64-unknown-linux-gnu'
2.595 info: latest update on 2023-12-28, rust version 1.77.0-nightly (89e2160c4 2023-12-27)
2.595 info: downloading component 'cargo'
3.274 info: downloading component 'rust-std'
```
---------
Signed-off-by: David Korczynski <david@adalogics.com>
libspdm is a sample implementation that follows the DMTF [SPDM
](https://www.dmtf.org/standards/spdm)specifications.
The SPDM standard enables authentication, attestation and key exchange
to assist in providing infrastructure security enablement.
Signed-off-by: Zhao, Zhiqiang <zhiqiang.zhao@intel.com>
Bumps introspector. The primary update is that we now expose all debug
information in an index file where each type is indexed by its address.
The address is the key used by LLVM, which is unique for each type.
There are additional helped features to make debug information look
prettier as it's quite verbose.
The goal is to assist making it easier to extract full type contexts.
Signed-off-by: David Korczynski <david@adalogics.com>
Google's internal fuzzers found tests that make `fuzz_regexp.c` exceed
stack memory. Turns out, QuickJS already has built-in mechanism for
tracking that stack size doesn't exceed a given limit - it's just that
limit isn't set for fuzzer tests by default
Setting the limit to 64kb as a reasonable default setting
Dongge Liu