Skip to content
New issue

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

#![no_std] Support #38

Open
zer0x64 opened this issue Apr 24, 2020 · 2 comments · May be fixed by #177
Open

#![no_std] Support #38

zer0x64 opened this issue Apr 24, 2020 · 2 comments · May be fixed by #177

Comments

@zer0x64
Copy link

zer0x64 commented Apr 24, 2020

The Arbitrary crate isn't #[no_std], which prevent fuzzing #![no_std] crates. For now can be worked around by using #![cfg_attr(not(feature = "fuzzing), no_std)] at the top of the fuzzed crate instead of #![no_std], but it would be better not to need this workaround.

Although I don't really see a use case of doing the actual fuzzing in a #![no_std] environment, is would be nice not to need any reference to std in the fuzzed crate.

AFAIK, the arbitrary crate doesn't really rely on std features and pretty much everything required can be fetched from the alloc create.

I forked the crate and started to try to make the change. The first roadbump I encountered is the quote crate used in arbitrary-derive, so I might need to open a simillar issue over there.

@frewsxcv
Copy link
Member

Thanks for opening this issue. We'd accept a PR for this if someone makes the necessary changes, but it doesn't seem high enough priority at this time to keep this GitHub Issue open.

@frewsxcv
Copy link
Member

After #63 merges, this will actually be a bit easier

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants