[Boost::Test] short form of catch_system_errors not working
Occasionally I need a core dump if testing goes wrong. Boost test have the following option ------------ Parameter: catch_system_errors Allows to switch between catching and ignoring system errors (signals). Command line formats: --[no_]catch_system_errors[=<boolean value>] -s[ <boolean value>] ------------------- I never managed to get short options to work and has to search for a long option exact name. Neither '-s no', '-s false' , -sno with or without quotes are not accepted. examples ----- $ test_app -s no Boost.Test WARNING: token "no" does not correspond to the Boost.Test argument and should be placed after all Boost.Test arguments and the -- separator. For example: test_app --random -- no ------ $ test_app "-s no" Invalid separator for the parameter catch_system_errors in the argument -s no ----- Is it a known bug? Best regards, Konstantin
Le 25/03/2018 à 21:24, Konstantin Kivi via Boost-users a écrit :
Occasionally I need a core dump if testing goes wrong. Boost test have the following option ------------ Parameter: catch_system_errors Allows to switch between catching and ignoring system errors (signals). Command line formats: --[no_]catch_system_errors[=<boolean value>] -s[ <boolean value>] ------------------- I never managed to get short options to work and has to search for a long option exact name.
Neither '-s no', '-s false' , -sno with or without quotes are not accepted.
examples ----- $ test_app -s no
Boost.Test WARNING: token "no" does not correspond to the Boost.Test argument and should be placed after all Boost.Test arguments and the -- separator. For example: test_app --random -- no ------ $ test_app "-s no"
Invalid separator for the parameter catch_system_errors in the argument -s no
-----
Is it a known bug?
Best regards, Konstantin
Please create a ticket on trac and I'll look at this. Thanks! Raffi
participants (2)
-
Konstantin Kivi -
Raffi Enficiaud