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

env: different error output with cannot unset '=': Invalid argument OSS-Fuzz issue 384591131 #6962

Closed
oss-fuzz-robot opened this issue Dec 17, 2024 · 5 comments
Labels

Comments

@oss-fuzz-robot
Copy link

OSS-Fuzz has found a bug in this project. Please see https://oss-fuzz.com/testcase?key=6592863400427520 for details and reproducers.

This issue is mirrored from https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=384591131 and will auto-close if the status changes there.

If you have trouble accessing this report, please file an issue at https://github.com/google/oss-fuzz/issues/new.

@sylvestre sylvestre changed the title OSS-Fuzz issue 384591131 env: different error output with cannot unset '=': Invalid argument OSS-Fuzz issue 384591131 Dec 17, 2024
@sylvestre
Copy link
Contributor

	Discrepancy detected: stderr differs
	Test completed with discrepancies for env: ["-0", "--chdir=/tmp"]
	Running test ["env", "-u="]
	Test Type: env
	Input: ["-u="]
	Rust stderr: cannot unset '': Invalid argument
	GNU stderr: cannot unset '=': Invalid argument
	Diff=
	-cannot unset '': Invalid argument
	+cannot unset '=': Invalid argument
	

@jovielarue
Copy link
Contributor

Hi @sylvestre, I'd like to try to tackle this issue if that's alright!

@cakebaker
Copy link
Contributor

@jovielarue sure, go ahead :)

@jovielarue
Copy link
Contributor

It looks like this issue is a duplicate of #6165 and #6166 and has had attempted to be fixed in #6172 and #6711; however it doesn't look like either of those fixes were complete.

It seems as though this issue is a result of clap parsing differing from the GNU/POSIX getopt standards. There was an issue on the clap repository attempting to foster a conversation with the clap developers to change this, but it has been denied as they don't want to introduce breaking changes.

Would it be beneficial for me to attempt to finish #6172 or #6711?

@sylvestre
Copy link
Contributor

Sure, sounds good, thanks :)
and well done for the investigation!

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

No branches or pull requests

4 participants