#875871 viking: Crashes with segmentation violation in gdk_draw_arc

Package:
viking
Source:
viking
Description:
GPS data editor, analyzer and viewer
Submitter:
Arnold Metselaar
Date:
2017-09-15 15:24:04 UTC
Severity:
important
#875871#5
Date:
2017-09-15 12:30:59 UTC
From:
To:
Dear Maintainer,

The program may be triggered zooming, panning or the addition of a piece of rote or track.
When I run viking under gdb I see a SIGSEGV and get a backtrace like this:

Thread 1 "viking" received signal SIGSEGV, Segmentation fault.
0x00007ffff72fb26a in gdk_draw_arc () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
(gdb) bt
#0  0x00007ffff72fb26a in gdk_draw_arc () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#1  0x00005555555e4318 in ?? ()
#2  0x00007ffff575c850 in g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00005555555df387 in ?? ()
#4  0x00005555556091da in ?? ()
#5  0x00005555555f8f32 in ?? ()
#6  0x00005555555fb899 in ?? ()
#7  0x00007ffff5a46f75 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x00007ffff5a58f82 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x00007ffff5a61bdc in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007ffff5a61fbf in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00005555555f635f in ?? ()
#12 0x00007ffff576d6aa in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff576da60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff576dd82 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff76bd3b7 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#16 0x00005555555d15a3 in ?? ()
#17 0x00007ffff24042b1 in __libc_start_main (main=0x5555555d12f0, argc=1, argv=0x7fffffffe708, init=<optimized out>,
    fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe6f8) at ../csu/libc-start.c:291
#18 0x00005555555d179a in ?? ()

It is likely that the problem exists in the upstreamn version as well.

Kind regards,
Arnold Metselaar
#875871#10
Date:
2017-09-15 15:08:20 UTC
From:
To:
Hi,

I have observed that viking is rather stable when the drawing of track points
and stops are both switched off and prone to crashing when they both switched
on, which happens to be the default setting.

Regards,
Arnold