Segfault when loading satellite to rviz about rviz_satellite HOT 8 CLOSED

Hi David,

Are you saying that rviz_satellite is crashing instantly, even before you can configure it in rviz?

Could you run rviz with GDB to see if we can catch something in the backtrace?

http://wiki.ros.org/roslaunch/Tutorials/Roslaunch%20Nodes%20in%20Valgrind%20or%20GDB

Thanks

from rviz_satellite.

ok I ran it with gdb and got this result

Thread 1 "rviz" received signal SIGSEGV, Segmentation fault.
0x00007fff771025a4 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4

On Wed, Jun 15, 2016 at 1:51 AM, Francois Chataigner <
[email protected]> wrote:

Hi David,

Are you saying that rviz_satellite is crashing instantly, even before you
can configure it in rviz?

Could you run rviz with GDB to see if we can catch something in the
backtrace?

http://wiki.ros.org/roslaunch/Tutorials/Roslaunch%20Nodes%20in%20Valgrind%20or%20GDB

Thanks

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AJuAIepOM3-dE3hDB9YgzzD68D9jYjYiks5qL68SgaJpZM4I1_0y
.

from rviz_satellite.

Ok and what does it say if you type "bt" (backtrace) in gdb?

from rviz_satellite.

Thread 1 "rviz" received signal SIGSEGV, Segmentation fault.
0x00007fff79c865a4 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
(gdb) bt
#0 0x00007fff79c865a4 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#1 0x00007ffff7de74ea in call_init (l=, argc=argc@entry=1,
argv=argv@entry=0x7fffffffdad8, env=env@entry=0x7fffffffdae8)
at dl-init.c:72
#2 0x00007ffff7de75fb in call_init (env=0x7fffffffdae8,
argv=0x7fffffffdad8,
argc=1, l=) at dl-init.c:30
#3 _dl_init (main_map=main_map@entry=0x1876be0, argc=1,
argv=0x7fffffffdad8,
env=0x7fffffffdae8) at dl-init.c:120
#4 0x00007ffff7dec712 in dl_open_worker (a=a@entry=0x7fffffffbb70)
at dl-open.c:575
#5 0x00007ffff7de7394 in _dl_catch_error (
objname=objname@entry=0x7fffffffbb60,
errstring=errstring@entry=0x7fffffffbb68,
mallocedp=mallocedp@entry=0x7fffffffbb5f,
operate=operate@entry=0x7ffff7dec300 <dl_open_worker>,
args=args@entry=0x7fffffffbb70) at dl-error.c:187
#6 0x00007ffff7debbd9 in _dl_open (
file=0x184c6b0 "/home/david/Paquetes/devel/lib//librviz_satellite.so",
mode=-2147483391,
caller_dlopen=0x7ffff111d862
<Poco::SharedLibraryImpl::loadImpl(std::__cxx11::basic_string<char,
std::char_traits, std::allocator > const&)+82>, nsid=-2,
argc=, argv=, env=0x7fffffffdae8)
at dl-open.c:660

On Wed, Jun 15, 2016 at 10:17 AM, Francois Chataigner <
[email protected]> wrote:

Ok and what does it say if you type "bt" (backtrace) in gdb?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AJuAIaEhXn62ehaPz98XmjnNbAlQrUrRks5qMCWTgaJpZM4I1_0y
.

from rviz_satellite.

is it fixable? im using ros kinetic

On Thu, Jun 16, 2016 at 6:17 PM, david rodriguez [email protected] wrote:

Thread 1 "rviz" received signal SIGSEGV, Segmentation fault.
0x00007fff79c865a4 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
(gdb) bt
#0 0x00007fff79c865a4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#1 0x00007ffff7de74ea in call_init (l=, argc=argc@entry
=1,
argv=argv@entry=0x7fffffffdad8, env=env@entry=0x7fffffffdae8)
at dl-init.c:72
#2 0x00007ffff7de75fb in call_init (env=0x7fffffffdae8,
argv=0x7fffffffdad8,
argc=1, l=) at dl-init.c:30
#3 _dl_init (main_map=main_map@entry=0x1876be0, argc=1,
argv=0x7fffffffdad8,
env=0x7fffffffdae8) at dl-init.c:120
#4 0x00007ffff7dec712 in dl_open_worker (a=a@entry=0x7fffffffbb70)
at dl-open.c:575
#5 0x00007ffff7de7394 in _dl_catch_error (
objname=objname@entry=0x7fffffffbb60,
errstring=errstring@entry=0x7fffffffbb68,
mallocedp=mallocedp@entry=0x7fffffffbb5f,
operate=operate@entry=0x7ffff7dec300 <dl_open_worker>,
args=args@entry=0x7fffffffbb70) at dl-error.c:187
#6 0x00007ffff7debbd9 in _dl_open (
file=0x184c6b0 "/home/david/Paquetes/devel/lib//librviz_satellite.so",
mode=-2147483391,
caller_dlopen=0x7ffff111d862
<Poco::SharedLibraryImpl::loadImpl(std::__cxx11::basic_string<char,
std::char_traits, std::allocator > const&)+82>, nsid=-2,
argc=, argv=, env=0x7fffffffdae8)
at dl-open.c:660

On Wed, Jun 15, 2016 at 10:17 AM, Francois Chataigner <
[email protected]> wrote:

Ok and what does it say if you type "bt" (backtrace) in gdb?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AJuAIaEhXn62ehaPz98XmjnNbAlQrUrRks5qMCWTgaJpZM4I1_0y
.

from rviz_satellite.

Hi, I was hoping that gdb would give us more info but there isn't much in the debug output you sent.

I don't have a setup running Ubuntu 16.04 so I'm not able to test I'm afraid... Is there any chance you have a 14.04 setup? So you can confirm that the plugin is running OK? I have been using it with 14.04 + ROS jade and it's been working great

from rviz_satellite.

I hace finales this week so Ill try to vmware it friday night and try it out
El jun. 21, 2016 6:00 AM, "Francois Chataigner" [email protected]
escribió:

Hi, I was hoping that gdb would give us more info but there isn't much in
the debug output you sent.

I don't have a setup running Ubuntu 16.04 so I'm not able to test I'm
afraid... Is there any chance you have a 14.04 setup? So you can confirm
that the plugin is running OK? I have been using it with 14.04 + ROS jade
and it's been working great

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AJuAITrtukiA_aNSHYCPS966ZNIQPj1Uks5qN9JagaJpZM4I1_0y
.

from rviz_satellite.

Confirmed for lunar and probably all later ros distros. CMakeLists.txt only checks for kinetic in line 8.

from rviz_satellite.