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

Hard to debug issue with commands not getting properly parsed in MSVC 2022 release builds #1105

Open
SaschaWillems opened this issue Dec 18, 2024 · 5 comments

Comments

@SaschaWillems
Copy link

We use this library for command line parsing in our Vulkan samples at https://github.com/KhronosGroup/Vulkan-Samples

I noticed that that commands with a value like this:

--shading-language hlsl

No longer work with MSVC in release builds only and we get an ExtrasError instead:

CLI11 Parse Error: [sample] The following arguments were not expected: hlsl --shading-language

A debug or release with debug info build works fine.

I tried to debug, which is kinda hard if it works in all builds with debug information and I'm out of clues. Updating to the latest version of CLI11 didn't help either.

Any ideas as to why this could happen, and why only in release mode?

@phlptp
Copy link
Collaborator

phlptp commented Dec 18, 2024

are you using the main release or the latest tagged release?

@SaschaWillems
Copy link
Author

We are using a recent commit from the main branch.

@phlptp
Copy link
Collaborator

phlptp commented Dec 18, 2024

Any chance you can bisect the commits and figure out which merge causes the issue?

@SaschaWillems
Copy link
Author

Bisecting might take some time, but I went back as far as tag v1.9.0 and the issue still persists. So I guess this is an issue on our side, but that code was written by a different maintainer. Any hints as to where I could look for the cause of that problem only showing up in release?

@phlptp
Copy link
Collaborator

phlptp commented Dec 18, 2024

If it predates 2.0 then that is a different matter, I was worried one of the recent fixes changed something. I will have to dig into it a bit more on exactly how you are using things. Do you have the exact compiler flags you are using to generate the error?

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