Skip to content

Command line option parsing issues #1412

@JamesRumble-IMG

Description

@JamesRumble-IMG

I noticed that the set of command line arguments we were previously no longer work properly (prior version we are using f5b1b7f)

The following command line arguments previously worked:
Vulkan-Samples/vulkan_samples --benchmark --stop-after-frame 100 --force-close sample multithreading_render_passes

Now it seems sample must be first with --benchmark --stop-after-frame 100 --force-close coming after the sample name.
I couldn't see any changes to the --help option to explain this. Is this expected behaviour?

While checking this I also noticed that incorrectly specifying --stop-after-frame 100 as --stop-after-frame=100 causes a segfault on

else if (optionIt->second->handle_option(argumentDeque))
. The command line argument is obviously wrong but I'd imagine the app shouldn't segfault.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions