ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Alpha's profile - activity

2021-07-24 10:26:58 -0500 received badge  Taxonomist
2015-04-29 01:59:23 -0500 received badge  Famous Question (source)
2014-03-03 20:44:48 -0500 received badge  Famous Question (source)
2014-02-09 10:58:00 -0500 received badge  Notable Question (source)
2014-02-04 20:36:47 -0500 received badge  Enthusiast
2014-01-31 09:42:01 -0500 received badge  Popular Question (source)
2014-01-31 07:21:15 -0500 answered a question Inappropriate ioctl for device

Well I figured out what caused it. The urdf file was using a hokuyo laser, which in turns uses the GPU to do calculations. Disabling the GPU usage fixed the segfault.

Disable it by changing

<sensor name="laser_scanner_sensor" type="gpu_ray">

and

<plugin filename="libgazebo_ros_gpu_laser.so" name="gazebo_ros_head_hokuyo_controller">

To

<sensor name="laser_scanner_sensor" type="ray">

and

<plugin filename="libgazebo_ros_laser.so" name="gazebo_ros_head_hokuyo_controller"></plugin></sensor></plugin></sensor>
2014-01-31 06:02:57 -0500 commented question Inappropriate ioctl for device

Thanks for the advice, I'll try the latest version of Gazebo (currently the default that comes with hydro) and post the result here.

2014-01-31 06:01:47 -0500 commented answer Inappropriate ioctl for device

Well the ioctl error will disappear (unknown if it is occuring or not, but it is not displayed) but the segfault remains. I was under the impression that the ioctl error and the segfault were related, but perhaps they are not. How else could I determine the cause of the segfault?

2014-01-31 01:42:18 -0500 asked a question Inappropriate ioctl for device

Hi,

I have an issue running the gazebo server. It always crashes with a segfault.

Here is the debug log:

http://pastebin.com/c51fvTz9

This is how I launch gazebo:

  <include file="$(find gazebo_ros)/launch/empty_world.launch">
    <arg name="debug" value="true">
 </arg></include>

I've looked around, more users seem to have this problem but there does not appear to be a definitive solution.

I run Ubuntu 12.04 with nvidia drivers (GT650M) installed by bumblebee. OpenGL appears to work (glxgears) and rviz works fine.

Any ideas?

Edit: this was using gazebo 1.9.3 and ROS Hydro

2014-01-27 22:54:42 -0500 received badge  Notable Question (source)
2013-11-12 20:22:59 -0500 commented answer Msg gen error (stray '#' in program)

Well it was indeed the line endings. I created the file with Notepad++ (my ROS environment is remote, I use windows to develop) which was on Windows line endings by default. Changing it to Unix/OSX format did the trick. Glad you already added to the bug report :)

2013-11-12 20:21:01 -0500 received badge  Supporter (source)
2013-11-12 20:20:59 -0500 received badge  Scholar (source)
2013-11-12 20:17:18 -0500 received badge  Popular Question (source)
2013-11-12 04:01:52 -0500 received badge  Editor (source)
2013-11-12 03:59:25 -0500 asked a question Msg gen error (stray '#' in program)

Hi there,

I'm building a program this message (Pose2DArray.msg):

Header header
geometry_msgs/Pose2D[] poses

But when I build it, with an empty main function, I get the following errors:

error: stray \ in program
error: stray # in program
error: stray \ in program
error: stray # in program
(more omitted)

This appears to be from the following, in Pose2DArray.h:

return "Header header \n\

\n\ geometry_msgs/Pose2D[] poses\n\
================================================================================\n\ MSG: std_msgs/Header\n\
# Standard metadata for higher-level stamped data types.\n\
# This is generally used to communicate timestamped data \n\
# in a particular coordinate frame.\n\
# \n\
# sequence ID: consecutively increasing ID \n\ uint32 seq\n\
#Two-integer timestamp that is expressed as:\n\
# * stamp.secs: seconds (stamp_secs) since epoch\n\
# * stamp.nsecs: nanoseconds since stamp_secs\n\
# time-handling sugar is provided by the client library\n\ time stamp\n\
#Frame this data is associated with\n\
# 0: no frame\n\
# 1: global frame\n\ string frame_id\n\ \n\
================================================================================\n\ MSG: geometry_msgs/Pose2D\n\
# This expresses a position and orientation on a 2D manifold.\n\ \n\ float64 x\n\ float64 y\n\ float64 theta\n\ ";   }

When I removed all that and replace it with

return "";

everything works. But since it is auto generated, the error re-appears later.

So I tried to remove the Header, so the msg was only

geometry_msgs/Pose2D[] poses

and everything works. Why can't I use Header here? Is this a bug or do I forget something?

edit: putting a comment in there ( # and some text) will also cause this