[bug] ROS launch can not load launch file that includes gazebo (program path 'PATH' is missing or invalid)

System info

Version: 1.58.0-insider Commit: 3e0c442a8ee9fdc037d627d70fe291f72af04cfd Date: 2021-06-16T05:18:57.982Z Electron: 12.0.11 Chrome: 89.0.4389.128 Node.js: 14.16.0 V8: 8.9.255.25-electron.0 OS: Linux x64 5.8.0-55-generic ROS VERSION: ROS 1 Noetic VSCODE-ROS VERSION:

what is the bug

This week I was not able to debug a ROS launch script anymore if it contained a launch script that loads the gzserver. Every time I try to launch such a file, it gives me the following error messages:

Further in the /gazebo_gui console, it gives the following error message:

The program '/opt/ros/noetic/lib/gazebo_ros/gzserver' has exited with code 42 (0x0000002a).

Repro steps

1. Download the following example repository.
2. Start the ROS: Gazebo launch (works) launch file that is found in the .vscode/launch.json file of the example_repository.
3. See the errors that appear.

expected behaviour

Some weeks ago, the launch file would still launch.

Vscode developer tools log

Extra info

• Bug is also present in the normal vscode version.
• Setting export DISPLAY=:0.0 doesn’t solve the issue.

[ooeygui]

@KoganOleg Thanks!

@rickstaa For this specific bug, I’m working on a fix to improve detecting of bat/sh/bash/cmd files so that it doesn’t just fail out right. I hope to have that committed in a few days. Once that bug fix is committed, I’ll close this issue. I have a couple of blocking things like this going into the 0.8.0 release.

[ooeygui]

gzserver and gzclient are shell scripts. Our code detects python, but not shell scripts, so it treats it as a binary program.

I’m going to add some code to detect this case and just launch it.