-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gazebo_yarp_controlboard crashes on Ubuntu 12.04 when activating callback #71
Comments
yep, on Alex's laptop, but didn't investigate it. Could it have anything to do with setting the initial position also? EDIT: now that I think about it, the crash happened in a situation that looked like waiting for an event that never got fired. The simulation got stuck for a few seconds before the actual crash happened |
gdb output? valgrind output? call stack before segfault? from your output On Wed, Mar 12, 2014 at 12:18 AM, arocchi notifications@github.com wrote:
|
@MirkoFerrati do you have experience in debugging shared libraries? Should gazebo also be compiled with debug symbols or just the shared library is fine? |
The shared library should be enough. We really have to learn how to debug On Wed, Mar 12, 2014 at 7:58 AM, arocchi notifications@github.com wrote:
|
gdb output (even if I have no cue what does it mean...): [Thread 0x7fffe0d17700 (LWP 5079) exited] |
ehm... yes, those lines give no big clues. Thanks |
no stack... |
For installing the gazebo with debug symbols you have to install the package gazebo-current-dbg . |
Yes @traversaro I have actually a similar log to the one you originally posted here. In fact installing gazebo_current-dbg gives you the debugging symbols. Heeeeeeelp!!! :D I will post my log as soon as I get the chance, but I remember the exact same methods you highlight in your original post. |
Guys please try also valgrind with gazebo-dgb and the plugin installed in On Sat, Mar 15, 2014 at 3:28 PM, jeljaik notifications@github.com wrote:
|
Ok, this is the backtrace from gazebo-current-dbg (gzserver):
|
Can you try to run this version of the plugin and post here the new output? (also if you have patience, I am still curious about valgrind output). |
Here is the gdb output of the gzserver with the "issue71" branch of gazebo_yarp_plugins:
|
also YARP should be compiled with debug symbols :P |
I really really need valgrind output now... I know it's slow but please just once! |
Wait, before that, can you please tell me what's inside /etc/apt/sources.list.d/gazebo-latest.list ? |
This is what's inside /etc/apt/sources.list.d/gazebo-latest.list : deb http://packages.osrfoundation.org/gazebo/ubuntu precise main This is the valgrind output (memcheck):
|
in my case it was a 64bit machine EDIT: I was imprecise too :) 64 bit OS |
I was imprecise: I was not asking if the machine is 32bit or 64bit, but if the operating system is 32bit or 64bit. |
Processor: Intel® Core™2 Duo CPU P8600 @ 2.40GHz × 2 |
We managed to solve the issue on the laptop of @jeljaik . |
scary, I will try this on Alex's laptop and get back to you |
I have no access to my Ubuntu machine right now... I will try that on On Wed, Mar 19, 2014 at 10:36 PM, arocchi notifications@github.com wrote:
|
Ok, we are still trying to investigate the details of the issue, if all the people still having this issue could post the output of the command: |
On my system: ii libboost-system-dev 1.48.0.2 Operating system (e.g. diagnostics support) library (default version) |
Ok.. I think this can be the problem.. at least with your configuration On 21/mar/2014, at 17:20, lorejam notifications@github.com wrote:
|
So, do you think I have to install gazebo from sources? |
I accidentally deleted the comment: this is the same configuration of our desktop running 12.04 and on which gazebo_yarp_plugins works. |
@traversaro are you sure about the libboost on the lab pc? On 21 Mar 2014, at 18:41, Silvio Traversaro notifications@github.com wrote:
|
Hi, I checked on Alex's computer, it has only 1.46 installed (Ubuntu 12.04).... |
Just a ping: gazebo 3 was released today with a lot of fixes, possibly this bug could be related to some of them. |
For related issue #90 the solution was to this one: #90 (comment) . |
Perfect, we have to mention in the README that is possible to encounter this problem, and how to fix it. Then we can close the issue. |
Fix in 4bf92a5 . |
A user running gazebo_yarp_plugins master, Gazebo 2.2 on Ubuntu 12.04 reported a crash on loading of gazebo_yarp_controlboard, both on the iCub model and on the toy double_pendulum model.
The output before the crash is:
From the output, I guess the crash is related in someway to the callback of the driver from gazebo, in particular this code:
Some of the walkman guys @EnricoMingo @MirkoFerrati @arocchi already experienced this issue or something similar?
The text was updated successfully, but these errors were encountered: