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

Allow analysis of debug builds, not just release builds. #82

Open
hydra opened this issue Nov 21, 2022 · 0 comments
Open

Allow analysis of debug builds, not just release builds. #82

hydra opened this issue Nov 21, 2022 · 0 comments

Comments

@hydra
Copy link
Contributor

hydra commented Nov 21, 2022

I have a use-case where I need to know how much MCU memory to devote to stack usage for code compiled in debug mode.

The tool currently always builds in release mode as it adds the --release argument to the rustc invocation.

Please can this restriction be changed? Maybe by way of a new command line argument that defaults to release mode? More specifically the cargo profile needs to be supported along with custom profiles.

See: https://doc.rust-lang.org/cargo/reference/profiles.html#custom-profiles

It seems there is some conditional code already that adds the --release argument, but the value it depends on is hard-coded.

See:
https://github.com/japaric/cargo-call-stack/blob/main/src/main.rs#L120
and
https://github.com/japaric/cargo-call-stack/blob/main/src/main.rs#L174-L176

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

1 participant