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

Could not resolve CoreCLR path. #63

Open
steamerg opened this issue Dec 9, 2024 · 1 comment
Open

Could not resolve CoreCLR path. #63

steamerg opened this issue Dec 9, 2024 · 1 comment

Comments

@steamerg
Copy link

steamerg commented Dec 9, 2024

Hi!

So I made a test application and the tool there runs well, but in my main application I want to use the tool (its a .Net Framework program, maybe thats the problem?) and I get this message: "Could not resolve CoreCLR path. For more details, enable tracing by setting COREHOST_TRACE environment variable to 1" and the program stops here. How can I solve this issue?
Thank you for your help!

@mschessler
Copy link
Contributor

Quoting from one of the articles:

Everyone is moving to .NET Core these days. But the migration can be slow, and there are many libraries that might never be ported to .NET Core. With libFuzzer and Windows support, SharpFuzz can now fuzz .NET Framework libraries, too! I didn’t have to do anything special to enable this feature, though: SharpFuzz has been targeting .NET Standard since the beginning. The only thing needed to support .NET Framework was the fuzzing engine that could run on Windows, and as you know from the previous section, libFuzzer satisfies that requirement.

Are you using libfuzzer natively on Windows for SharpFuzz ? It should work with .Net Framework then.

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

No branches or pull requests

2 participants