[SOLVED] JLinkRTTViewer segmentation fault (v6.46g)

wifijacob · June 24, 2019 at 3:28 PM

hi,
i'm getting this segmentation fault when trying to use jlinkrttviewer (it occurs when clicking on the device selector):

Code

Thread 1 "JLinkRTTViewer" received signal SIGSEGV, Segmentation fault.
0x0000000000421080 in ?? ()
(gdb) bt
#0  0x0000000000421080 in ?? ()
#1  0x0000000000413be8 in ?? ()
#2  0x0000000000415aa3 in ?? ()
#3  0x00007ffff6d8f010 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007ffff769c4d1 in QComboBox::activated(int) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#5  0x00007ffff769c58e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#6  0x00007ffff769cd29 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x00007ffff6d8f010 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007ffff794dda2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x00007ffff7697faa in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x00007ffff6d7aa76 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007ffff72a7fbc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007ffff72af0d6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007ffff6d7a90d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x00007ffff72ae6dd in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#15 0x00007ffff732cd7c in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#16 0x00007ffff732bc83 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#17 0x00007ffff7355542 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#18 0x00007ffff5239197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff52393f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007ffff523949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007ffff6dab2ae in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#22 0x00007ffff7355616 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#23 0x00007ffff6d7918f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x00007ffff6d794f5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#25 0x00007ffff778aa3c in QDialog::exec() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#26 0x0000000000418155 in ?? ()
#27 0x000000000041b353 in ?? ()
#28 0x0000000000416423 in ?? ()
#29 0x00007ffff597c830 in __libc_start_main (main=0x4162a0, argc=1, argv=0x7fffffffd3e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd3d8) at ../csu/libc-start.c:291
#30 0x0000000000411b69 in ?? ()
#31 0x00007fffffffd3d8 in ?? ()
#32 0x000000000000001c in ?? ()
#33 0x0000000000000001 in ?? ()
#34 0x00007fffffffd836 in ?? ()
#35 0x0000000000000000 in ?? ()

Display More

i'm using ubuntu 16.04.

SEGGER - Leon · June 25, 2019 at 10:00 AM

Hello,

Thank you for your inquiry.
We are sorry to hear you are having issues with one of our products.

Are you referring to the [...] button for "Specify Target Device" (Please see the attached screenshot for reference)?

I just tried this on ubuntu 16.04 and the device selection dialog worked as expected.
Same goes for ubuntu 18.04.

Could you please tell me if you do anything else before clicking the [...] button, or do you just open RTTViewer and click the button immedieately?

wifijacob · June 26, 2019 at 10:58 AM

Hi,
I managed to reproduce by having two J-Links connected to the computer, clicking the target device drop-down and select a device.

Thanks, Jacob

SEGGER - Leon · June 28, 2019 at 6:05 PM

Hello Jacob,

Could you please tell me how you start the J-Link RTT Viewer?
I was able to reproduce the error you describe when executing the J-Link RTT Viewer from a directory
which is different from the directory that the J-Link RTT Viewer resides in.

Have you tried executing the J-Link RTT Viewer from its directory?
For example by calling

cd [...]/JLink_Linux_V646g_x86_64/

./JLinkRTTViewerExe

wifijacob · July 1, 2019 at 8:34 AM

Hello,
I am not starting it from the directory it's located - so we're probably seeing the same.

It should not cause a segmentation fault, however. That indicates that something is not right.

Thanks, Jacob

SEGGER - Leon · July 2, 2019 at 3:13 PM

Hello Jacob,

You are right, that behavior is not intentional and it has been fixed already.
It was caused by the different behavior, depending on where the application was executed from.
This will be fixed with the next release of the J-Link software package.

Stay up-to-date regarding J-Link:
https://www.segger.com/notification/s…php?prodid=7,94

Participate now!