Bug report
Required Info:
- Operating System:
- Installation type:
- Version or commit hash:
- DDS implementation:
- Client library (if applicable):
Steps to reproduce issue
On any node, set a parameter with a string value containing a non-ASCII character:
ros2 param set /talker value 'añd'
Now, attempt to retrieve that same parameter
ros2 param get /talker value
Expected behavior
Either ros2 param get succesfully retrieving the value or ros2 param set complaining about the invalid value. Since wstrings are not fully supported yet (see design proposal), I'm inclined for the latter.
Actual behavior
CLI segfaults.