While the controller is still in memory you can query the values of some variables in order to understand what happened. The line 106 of the source file "soccer_supervisor.c" must be examined closely. Webots GUI is composed of four principal windows: the 3D window that displays and allows you to interact with the 3D simulation, the Scene tree which is a hierarchical representation of the current world, the Text editor that allows you to edit source code, and finally, the Console that displays both compilation and controller outputs. The if condition is not necessary, it simply adds a 10 step delay before the. Therefore it seems that the problem is caused by an illegal use of the sprintf function in the run function. Cyberbotics - Robotics simulation with Webots. In this example we will assume that the sprintf function is OK, because it is in a system library. #0 0x00cd6dd5 in _IO_str_overflow_internal() from /lib/tls/libc.so.6 #1 0x00cd596f in _IO_default_xsputn_internal() from /lib/tls/libc.so.6 #2 0x00cca9c1 in _IO_padn_internal() from /lib/tls/libc.so.6 #3 0x00cb17ea in vfprintf() from /lib/tls/libc.so.6 #4 0x00ccb9cb in vsprintf() from /lib/tls/libc.so.6 #5 0x00cb8d4b in sprintf() from /lib/tls/libc.so.6 #6 0x08048972 in run(duration=0) at soccer_supervisor.c:106 #7 0x08048b0a in main() at soccer_supervisor.c:140īy examining carefully the call stack you can locate the source of the error. to give a step towards more realistic experiments using e-pucks on Webots. This can be achieved by adding this line to the controller's Makefile: Other additional features such as the debug possibility for real platforms. The first step is to recompile the controller code with the -g flag, in order to add debugging information to the executable file. On Windows GDB can be installed for example from the MSYS2 environment with the mingw-w64-x86_64-gdb package as indicated in the optional dependencies of the Windows installation instructions. The following example assumes that there is a problem with the "soccer_supervisor" controller and indicates how to proceed with the debugging. Note that the crash of a controller is almost certainly caused by an error in the controller code, because an error in Webots would have caused Webots to crash.įortunately, the GNU debugger ( gdb) can usually help finding the reason of the crash. Thank you in advance I tried to update the driver, but it had no effect. RT hwchase17: HumanInputLLM A LLM wrapper that: 1. What could be the cause Operating system Windows 8.1, video cards Intell, AMD. each time one module finishes its planing than the Webots should calculate the next simulation step dependent upon the output of the module. I can not understand the reasons for its occurrence. Is it possible to calculate the Webots simulation step programatically, i.e. In this example the "soccer_supervisor" has crashed. When launching Webots instead of a scene in the 3d View window, I sometimes get a black screen. If one of your robot controllers is missing in the list (or appearing as ) this confirms that it has crashed and therefore blocked the simulation. On macOS, use rather ps -x and on Windows use the Task Manager for this.
0 Comments
Leave a Reply. |