Revision history [back]

For seeing more information with roslaunch you can try roslaunch -v <package-name> <launch-name> to request verbosity output.

However, when I had the same error, the problem was a non-printing character in the file.

You can try to confirm by looking at a binary dump of the file with hexdump -C mylaunch.launch.

Delete these characters works for me.

For seeing more information with roslaunch you can try roslaunch -v <package-name> <launch-name> to request verbosity output.

However, when I had the same error, the problem was a non-printing character in the file.

You can try to confirm by looking at a binary dump of the file with hexdump -C mylaunch.launch.

Delete these characters works for me.

For seeing more information with roslaunch you can try roslaunch -v <package-name> <launch-name> to request verbosity output.

However, when I had the same error, the problem was a non-printing character in the file.

You can try to confirm by looking at a binary dump of the file with hexdump -C mylaunch.launch.

Delete these characters works for me.

Maybe it is in ~/.ros/log.

For seeing more information with roslaunch you can try roslaunch -v <package-name> <launch-name> to request verbosity output.

However, when I had the same error, the problem was a non-printing character in the file.

You can try to confirm by looking at a binary dump of the file with hexdump -C mylaunch.launch.

Delete these characters works for me.