We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential unaligned read
atty
0.2.14
On windows, atty dereferences a potentially unaligned pointer.
In practice however, the pointer won't be unaligned unless a custom global allocator is used.
In particular, the System allocator on windows uses HeapAlloc, which guarantees a large enough alignment.
System
HeapAlloc
A Pull Request with a fix has been provided over a year ago but the maintainer seems to be unreachable.
Last release of atty was almost 3 years ago.
The below list has not been vetted in any way and may or may not contain alternatives;
See advisory page for additional details.
The text was updated successfully, but these errors were encountered:
For anyone reading this: atty is only in the dependency tree for the benchmarking crate (due to criterion):
atty v0.2.14 └── criterion v0.4.0 [dev-dependencies] └── deterministic-bloom-benches v0.1.0 (/home/philipp/program/work/deterministic-bloom/deterministic-bloom-benches)
The fix is to update to criterion 0.5.1.
Sorry, something went wrong.
No branches or pull requests
atty
0.2.14
On windows,
atty
dereferences a potentially unaligned pointer.In practice however, the pointer won't be unaligned unless a custom global allocator is used.
In particular, the
System
allocator on windows usesHeapAlloc
, which guarantees a large enough alignment.atty is Unmaintained
A Pull Request with a fix has been provided over a year ago but the maintainer seems to be unreachable.
Last release of
atty
was almost 3 years ago.Possible Alternative(s)
The below list has not been vetted in any way and may or may not contain alternatives;
See advisory page for additional details.
The text was updated successfully, but these errors were encountered: