-
Notifications
You must be signed in to change notification settings - Fork 911
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
rosconsole segfault when ROSCONSOLE_FORMAT uses ${logger} #342
Comments
Can you post the output of |
After you give us that can you try |
Packages are already up to date (but ran again anyway).
|
Nothing happens when you do the |
No, I mean I already ran that today. |
I just compiled your example and it ran without any problem for me (on Quantal with up-to-date packages). |
Your example and rviz run here on precise, quantal and raring. Did you do an |
What does your |
My package is the default created by |
yes |
I disabled my .bashrc just now and only ran:
I still have a segfault :-/ |
I can't reproduce the segfault:
|
We're looking at the versions of packages you have listed in your gist, but I'm not sure what else it could be. Longshots:
|
Another long shot, does |
This removed: But it still doesn't work. Very frustrating... |
Fixed it, new terminal were sourcing a bad script somewhere... |
Ok, can you close this please? |
I've found the issue, and its related to the logger level issues ros-drivers/hokuyo_node#8 you guys have been addressing. As documented on ros.org I set my rosconsole format from my
After a recent debian update this week, I believe this broke. I get segfaults from all ros nodes using rosconsole. I really like the feature of having better ROS console lines other than time, so I'd like this fixed or a substitute made. Also, perhaps we should tell ros users? I just spent 2+ hours tracking down this bug. |
I updated the issue title to reflect that. With that environment variable I can reproduce and look into the problem. Thanks for narrowing it down. |
I created a pull request to fix this bug: #343 @davetcoleman Can you please clone the branch of the pull request into your workspace, recompile and confirm that this fixes the problem for you, too? |
Will do today |
I have tested the fix, it works, thanks! |
fix rosconsole segfault when using ROSCONSOLE_FORMAT with (fix #342)
…gfault fix rosconsole segfault when using ROSCONSOLE_FORMAT with (fix ros#342)
None of my ROS packages run anymore (segfault), it worked a few days ago and I didn't change the code. I did play with getting Gazebo 3.0 and drcsim working, and I switched to Groovy for a few minutes for testing Atlas. Now I'm back on Hydro on Precise. I have a local fresh roscore running.
I have a simple program for testing:
My CMake is an empty package except this test:
When I run this binary it crashes on the ROS_INFO part.
GDB Backtrace:
Also, I have installed from debian:
liblog4cxx10 0.10.0
liblog4cxx10-dev 0.10.0
ros-hydro-rosconsole 1.9.53
The text was updated successfully, but these errors were encountered: