-
-
Notifications
You must be signed in to change notification settings - Fork 467
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
planning_display segfaults rviz (ros-pkg ticket #960) #78
Comments
[anonymous] It seems this=0x0 in planning models, so the call is made on an invalid instance. Are you sure bot rviz & planning_models are up to date and built ? The function signature used no longer exists. |
[isucan] I actually get a segfault from mechanism model: {{{ |
[gerkey] I was up-to-date when I got the original crash. Now I get a similar but slightly different backtrace: |
[sglaser] Ioan: Could you post the backtrace from the crash? |
[isucan] Here it is: {{{ |
[isucan] The actual backtrace this time... {{{ |
[sglaser] I fixed the crash Ioan is having in r11408 |
[isucan] it seems to work; closing bug |
[gerkey] As an addendum, I encountered another segfaul with planning_display. In the end, it was because I hadn't entered anything for the Robot Description property. I added a check for this case to prevent the crash. It's checked in on the tabletop_manipulation_feb-2009 branch, which I'll merge to trunk next week. |
I get the following gdb backtrace by roslaunching tabletop_manipulation/sim.launch, then running rviz, enabling Planning, with Visual enabled and Collision disabled. Seems pretty repeatable.
{{{
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb35ee730 (LWP 21778)]
0xb7e3cdf5 in planning_models::KinematicModel::computeTransforms (this=0x0,
params=0xa873b830, groupID=-1)
at /u/gerkey/code/personalrobots/world_models/robot_models/planning_models/src/kinematic.cpp:82
82 assert(m_built);
(gdb) bt
#0 0xb7e3cdf5 in planning_models::KinematicModel::computeTransforms (
#1 0xb6b07e22 in rviz::PlanningDisplay::update (this=0xa863b298,
#2 0xb6a961c4 in rviz::VisualizationManager::onUpdate (this=0x87c4340,
#3 0xb619a0e1 in wxAppConsole::HandleEvent ()
from /usr/lib/libwx_baseu-2.8.so.0
#4 0xb6241b88 in wxEvtHandler::ProcessEventIfMatches ()
from /usr/lib/libwx_baseu-2.8.so.0
#5 0xb6241d74 in wxEvtHandler::SearchDynamicEventTable ()
from /usr/lib/libwx_baseu-2.8.so.0
#6 0xb6241e33 in wxEvtHandler::ProcessEvent ()
from /usr/lib/libwx_baseu-2.8.so.0
---Type to continue, or q to quit---
#7 0xb6552921 in wxTimerBase::Notify ()
from /usr/lib/libwx_gtk2u_core-2.8.so.0
#8 0xb642dec5 in ?? () from /usr/lib/libwx_gtk2u_core-2.8.so.0
#9 0xb493a436 in ?? () from /usr/lib/libglib-2.0.so.0
#10 0x087c2398 in ?? ()
#11 0xb600ea0c in __pthread_mutex_unlock_usercnt ()
from /lib/tls/i686/cmov/libpthread.so.0
#12 0xb4939cc6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#13 0xb493d083 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x0808cf10 in ?? ()
#15 0x00000000 in ?? ()
}}}
trac data:
The text was updated successfully, but these errors were encountered: