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.

Sign up for GitHub

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

Jump to bottom

"start" argument conflated with cargo subcommand #99

Open
chrysn opened this issue Jun 27, 2023 · 0 comments · May be fixed by #105
Open

"start" argument conflated with cargo subcommand #99

chrysn opened this issue Jun 27, 2023 · 0 comments · May be fixed by #105

Comments

@chrysn
Copy link

chrysn commented Jun 27, 2023

When cargo call-stack is called through cargo, the argv it sees is the unmodified `['cargo', 'call-stack', '--target', 'some-triple-triple', 'mystartsym']. Thus, the parser reports the start argument "mystartsym" as unexpected argument.

I'm not sure how this is best fixed; for a workaround, I'm calling it as ~/.cargo/bin/cargo-call-stack instad of cargo call-stack; this appears to necessitate setting a rustup override for nightly (as there is no place to put the +nightly).
mauricelam pushed a commit to mauricelam/cargo-call-stack that referenced this issue Sep 13, 2023
Fix positional arguments
a5498e7 
Add a cargo-subcommand argument so that when invoked from cargo the
positional arguments ("start") parse from the correct value.

Fix japaric#99
@mauricelam mauricelam linked a pull request Sep 13, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix positional arguments mauricelam/cargo-call-stack
1 participant
@chrysn