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

Tests & fixes for Boost.Test UTF command-line parsing. #18

Closed

Conversation

jurko-gospodnetic
Copy link
Contributor

UTF seems to have some serious issues with its command-line parsing. :-(

This pull request adds a test module for it, and fixes one of the problems - a segfault that occurs if you attempt to pass it an argument with a leading embedded space character or an empty string as the initial but not only argument.

There are other problems with this command-line handling, but I'll add failing tests for some of them as a separate pull request based on this one.

Best regards,
Jurko Gospodnetić

Currently implemented tests are still far from a complete test suite but they do
represent a good starting point for adding related tests in the future.
The bug is triggered by passing a command-line argument containing a leading
space character or by passing an empty leading command-line argument with an
additional argument after it.

Several of the newly added tests currently only check whether the test crashes
and not the command-line arguments left over after UTF processing. This is so
because the current UTF implementation does not seem to handle arguments with
embedded spaces correctly and that seems like a separate issue.
@rogeeff
Copy link
Contributor

rogeeff commented Sep 7, 2015

I am completely rewriting CLA support for next release. It'll address lots of issues including these.

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

Successfully merging this pull request may close these issues.

2 participants