Segmentation fault after last update (Klavaro)
Closed, ResolvedPublic

Description

Hello there,

After the last update this morning, I got a segmentation fault when running the klavaro package through the terminal. I ran the GNU Debugger to give you more details (package and kernel version at the end):

~$ gdb klavaro 
GNU gdb (Debian 8.2-1) 8.2
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from klavaro...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/klavaro 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff3759700 (LWP 7025)]
[New Thread 0x7ffff2f36700 (LWP 7026)]
[New Thread 0x7ffff2708700 (LWP 7027)]
[New Thread 0x7ffff1eff700 (LWP 7028)]
[New Thread 0x7ffff1375700 (LWP 7030)]

(klavaro:7021): Gtk-WARNING **: 13:43:45.253: Content added to the action area of a dialog using header bars

(klavaro:7021): Gtk-WARNING **: 13:43:45.254: Content added to the action area of a dialog using header bars

Thread 1 "klavaro" received signal SIGSEGV, Segmentation fault.
__strchrnul_sse2 () at ../sysdeps/x86_64/multiarch/../strchr.S:32
32	../sysdeps/x86_64/multiarch/../strchr.S: Aucun fichier ou dossier de ce type.
(gdb) bt
#0  __strchrnul_sse2 () at ../sysdeps/x86_64/multiarch/../strchr.S:32
#1  0x00007ffff6ec3c49 in __find_specmb (
    format=0xfffffffff14de3ed <error: Cannot access memory at address 0xfffffffff14de3ed>) at printf-parse.h:108
#2  _IO_vfprintf_internal (s=s@entry=0x7fffffffdde0, 
    format=format@entry=0xfffffffff14de3ed <error: Cannot access memory at address 0xfffffffff14de3ed>, ap=ap@entry=0x7fffffffdf50) at vfprintf.c:1315
#3  0x00007ffff6f7e408 in __GI___vasprintf_chk (result_ptr=0x7fffffffdf30, flags=1, 
    format=0xfffffffff14de3ed <error: Cannot access memory at address 0xfffffffff14de3ed>, args=0x7fffffffdf50) at vasprintf_chk.c:66
#4  0x00007ffff72fcef9 in g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ffff72d655d in g_strdup_vprintf ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007ffff72d6619 in g_strdup_printf ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x0000555555565048 in main ()
(gdb) quit
A debugging session is active.

	Inferior 1 [process 7021] will be killed.

Quit anyway? (y or n) y


klavaro --version
3.03


$ hostnamectl

  Operating System: PureOS
            Kernel: Linux 4.18.0-2-amd64
      Architecture: x86-64

Thank you for this report. I believe that this should go upstream into the Klavaro software itself

jeremiah.foster triaged this task as "Low" priority.Jan 25 2019, 5:19 PM

Thank you for your reply. How can we upstream this issue?

anonymized01 added a comment.EditedFeb 4 2019, 1:57 AM

Latest update fixed the issue.

jeremiah.foster closed this task as "Resolved".Feb 4 2019, 2:46 PM
jeremiah.foster claimed this task.

Glad to hear that the update helped!

Add Comment