Ask Your Question

rqt then choosing rviz plugin -> core dump

asked 2013-01-08 02:49:43 -0600

TommyP gravatar image

updated 2013-01-08 05:29:49 -0600

joq gravatar image

Start rqt and choose rviv plugin (in groovy):

tompe@heyer:~$ rqt
python: /build/buildd/ogre-1.7.4/OgreMain/include/OgreSingleton.h:80: Ogre::Singleton<T>::Singleton() [with T = Ogre::LogManager]: Assertion `!ms_Singleton' failed.
Aborted (core dumped)

Am I doing something wrong or is really this so buggy that it does not even start?

edit retag flag offensive close merge delete


What Linux distro and release are you running?

joq gravatar imagejoq ( 2013-01-08 05:32:38 -0600 )edit

I tested in Ubuntu 12.04 (i686). The same problem at home with 12.04 (x86_64).

TommyP gravatar imageTommyP ( 2013-01-08 07:54:13 -0600 )edit

Seems to work now for me with the latest version of the groovy Ubuntu packages.

TommyP gravatar imageTommyP ( 2013-02-07 01:22:43 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2013-01-08 06:48:58 -0600

mjcarroll gravatar image

updated 2013-02-12 02:14:30 -0600

I can confirm this on 12.04 (x64)/Groovy. I found a related issue on github already: There are a few similar issues in the rqt tracker that have been closed, so perhaps it hasn't been pushed out to the public yet?


I believe that this fixes it (it does on my system).

It's a one-line edit, so it should be pretty easy to patch rviz and build from source on your own system.


Fixed in latest debs.

edit flag offensive delete link more


It still does not work after today's groovy package updates.

TommyP gravatar imageTommyP ( 2013-01-09 04:19:57 -0600 )edit

I have exactly the same issue, under Ubuntu 12.04, groovy (under virtual box).

clark gravatar imageclark ( 2013-01-09 13:53:19 -0600 )edit

Re your fix: Should there be a new in the getSingletonPtr line? (I haven't checked or tested anything! Just looks odd to me)

dornhege gravatar imagedornhege ( 2013-01-10 05:03:44 -0600 )edit

I believe that getSingletonPtr returns a pointer to the already-created instance, and is not allocating a new instance.

mjcarroll gravatar imagemjcarroll ( 2013-01-10 05:11:23 -0600 )edit

The OGRE docs indicate that if you bring up an OgreRoot before you bring up a LogManager, it will instantiate one for you, thus causing the singleton assert error when you try to re-instantiate. The LogManager constructor should only be called before OgreRoot, which is not what is happening.

mjcarroll gravatar imagemjcarroll ( 2013-01-10 05:20:32 -0600 )edit

I was only referring to the diff in the pull request. It does something like new getSingletonPtr() instead of just getsSingletonPtr(), but I really haven't checked or tested anything in that regard. Just looked wrong to me.

dornhege gravatar imagedornhege ( 2013-01-10 05:30:36 -0600 )edit

Ah, sorry about that. Yes, that pull request is incorrect, and the problem is also a little bit deeper. It appears as though Dave has already come up with a fix that will be released shortly.

mjcarroll gravatar imagemjcarroll ( 2013-01-10 05:40:59 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2013-01-08 02:49:43 -0600

Seen: 514 times

Last updated: Feb 12 '13