minorbug(env): when using $'\xFF' with -S or without it, an unknown error reported
Open
Nobody has claimed this yet.
U - env
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
Hi, uutils mainteners
like the previous issue with the a/ when it is a directory however in that time, when passing $'\xFF', as i see env returns unknown errors
relunsec@relunsec:~/software/coreutils/target/debug$ ./env $'\xFF'
env: unknown error: execvp failed
relunsec@relunsec:~/software/coreutils/target/debug$ ./env -S $'\xFF'
env: unknown error: execvp failed
relunsec@relunsec:~/software/coreutils/target/debug$
while the gnu one shows known and correct error messages not unknown one
relunsec@relunsec:~/software/coreutils/target/debug$ gnuenv $'\xFF'
gnuenv: ‘\377’: Invalid or incomplete multibyte or wide character
relunsec@relunsec:~/software/coreutils/target/debug$ gnuenv -S $'\xFF'
gnuenv: ‘\377’: Invalid or incomplete multibyte or wide character
relunsec@relunsec:~/software/coreutils/target/debug$
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with env $'\xFF' and env -S $'\xFF', then inspect the env command's handling of execvp failures and invalid byte arguments. Compare the resulting diagnostics with GNU env; done means both forms report a specific invalid-or-incomplete multibyte error instead of "unknown error".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100