Solved pluma stack overflow / signal abort when hit ctrl-c, ctrl-s or similar

freebsd_noob

Active Member

Reaction score: 64
Messages: 177

Hi,

i use MATE dektop and the pluma text editor is unusable since it crashes with a stack overflow when i press CTRL-C, CTRL-S or similar:
Code:
pluma[1229]: stack overflow detected; terminated
kernel: pid 1229 (pluma), jid 0, uid 1001: exited on signal 6 (core dumped)


There is a bug report in the official github repository here https://github.com/mate-desktop/pluma/issues/503 but no solution yet.

System is FreeBSD 12.1-RELEASE-p2 (i386).

There is a ~30MB core dump in my home:
Code:
[xxx@xxx ~]$ gdb /usr/local/bin/pluma
GNU gdb (GDB) 8.3.1 [GDB v8.3.1 for FreeBSD]
Copyright (C) 2019 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 "i386-portbld-freebsd12.0".
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 /usr/local/bin/pluma...
(No debugging symbols found in /usr/local/bin/pluma)
(gdb) core pluma.core
[New LWP 100244]
[New LWP 100516]
[New LWP 100517]
[New LWP 100518]
[New LWP 100523]
Core was generated by `pluma'.
Program terminated with signal SIGABRT, Aborted.
#0  0x291ffa83 in kill () from /lib/libc.so.7
[Current thread is 1 (LWP 100244)]
(gdb) where
#0  0x291ffa83 in kill () at /lib/libc.so.7
#1  0x291ffa38 in  () at /lib/libc.so.7
#2  0x291ff97b in  () at /lib/libc.so.7
#3  0x0809bb4d in  ()
#4  0x2886abf7 in  () at /usr/local/lib/libgtk-3.so.0
#5  0x28f93a51 in  () at /usr/local/lib/libgobject-2.0.so.0
#6  0x28f93268 in  () at /usr/local/lib/libgobject-2.0.so.0
#7  0x28faa6cf in g_signal_emit_valist () at /usr/local/lib/libgobject-2.0.so.0
#8  0x28faacc7 in g_signal_emit () at /usr/local/lib/libgobject-2.0.so.0
#9  0x2880da72 in  () at /usr/local/lib/libgtk-3.so.0
#10 0x2880d7c2 in gtk_widget_event () at /usr/local/lib/libgtk-3.so.0
#11 0x28686730 in gtk_propagate_event () at /usr/local/lib/libgtk-3.so.0
#12 0x2868623a in gtk_main_do_event () at /usr/local/lib/libgtk-3.so.0
#13 0x28ab89ac in  () at /usr/local/lib/libgdk-3.so.0
#14 0x28af7f53 in  () at /usr/local/lib/libgdk-3.so.0
#15 0x29017189 in g_main_context_dispatch () at /usr/local/lib/libglib-2.0.so.0
#16 0x2901759e in  () at /usr/local/lib/libglib-2.0.so.0
#17 0x29017931 in g_main_loop_run () at /usr/local/lib/libglib-2.0.so.0
#18 0x28685943 in gtk_main () at /usr/local/lib/libgtk-3.so.0
#19 0x08069471 in main ()
(gdb)


What to do?
 
OP
freebsd_noob

freebsd_noob

Active Member

Reaction score: 64
Messages: 177

I did a few tests and this happens if you install FreeBSD i386 on an AMD64 machine. Installing the 64bit version of FreeBSD fixed it.
 
Top