GeezerVison is showing github.com — Update Rust crate libfuzzer-sys to 0.4.7 by renovate[bot] · Pull Request #71 · uutils/diffutils
Conversation
This PR contains the following updates:
| Package |
Type |
Update |
Change |
| libfuzzer-sys |
dependencies |
patch |
0.4 -> 0.4.7 |
Release Notes
rust-fuzz/libfuzzer (libfuzzer-sys)
Compare Source
Released 2023-08-10.
Added
- Added the
link_libfuzzer cargo feature. This feature is on by default and
preserves the existing behavior of statically linking libfuzzer. You can
disable it if you are linking your own version of libfuzzer some other way, or
another library that provides the same ABI as libfuzzer.
Compare Source
Released 2023-01-26.
Fixed
- Fixed a potential name conflict in functions generated by the
fuzz_target!
macro.
- Fixed potential stale builds when updating custom libfuzzers to link against.
Compare Source
Released 2022-10-18.
Added
- Added the ability to tell libfuzzer whether to keep files inputs in the corpus
or not. See the Corpus type and extended documentation for the
fuzz_target! macro for details.
Changed
- Ensured that there is always at least one inline-never frame on the stack per
fuzz target. This helps prevent oss-fuzz from "deduplicating" different bugs
from different fuzz targets into the same bug.
Compare Source
Released 2022-09-01.
Changed
- Updated to
libFuzzer commit df90d22 (release/15.x).
- LLVM 16's upcoming change to build requirements to C++17
necessitate reflecting those changes. (libFuzzer updates contain C++14 code)
- Drastically reduce build times by using parallel C++ compilation jobs
- Updated
rand dependency from 0.8.3 to 0.8.5
- Updated
flate2 dependency from 1.0.20 to 1.0.24
Compare Source
Released 2020-03-03.
Changed
- Updated to
libFuzzer commit 60e32a1.
Fixed
- Fixed an issue where the
fuzz_target! macro would sometimes expand to
versions of itself that were not $crate prefixed and would result in "error:
cannot find macro fuzz_target in this scope" if the caller didn't import the
macro but used the qualified version of it instead.
Compare Source
Released 2020-05-26.
Changed
- Improved performance of checking for whether
cargo fuzz is requesting the
std::fmt::Debug output of an input or not. This is always false during
regular fuzzing, so making this check faster should give slightly better
fuzzing throughput.
Compare Source
Released 2020-05-13.
Added
Changed
- Upgraded libfuzzer to llvm/llvm-project's
70cbc6d.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
codecov
Bot
commented
May 1, 2024
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
|
All modified and coverable lines are covered by tests ✅
Project coverage is 75.46%. Comparing base (1f896ca) to head (767c6f6).
Additional details and impacted files
@@ Coverage Diff @@
## main #71 +/- ##
==========================================
- Coverage 75.69% 75.46% -0.23%
==========================================
Files 10 10
Lines 2925 2935 +10
Branches 737 743 +6
==========================================
+ Hits 2214 2215 +1
- Misses 538 547 +9
Partials 173 173 Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.