|
| From: | anonymous |
| Subject: | [Octave-bug-tracker] [bug #51413] core dump when started via Alt-F2 |
| Date: | Fri, 7 Jul 2017 08:43:45 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0 |
URL:
<http://savannah.gnu.org/bugs/?51413>
Summary: core dump when started via Alt-F2
Project: GNU Octave
Submitted by: None
Submitted on: Fri 07 Jul 2017 12:43:43 PM UTC
Category: Performance
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Assigned to: None
Originator Name: Matthias Bodenbinder
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
Release: 4.2.1
Operating System: GNU/Linux
_______________________________________________________
Details:
I can run octave out of a terminal. That works fine. But when I use the Alt-F2
dialog of the cinnamon desktop octave is generating a core dump. The same is
true with MATE desktop.
I am using Manjaro.
Jul 07 14:41:10 manjaro systemd-coredump[28187]: Process 28182 (octave-gui) of
user 1000 dumped core.
Stack trace of thread 28182:
#0 0x00007fb0abb0f670 raise
(libc.so.6)
#1 0x00007fb0abb10d00 abort
(libc.so.6)
#2 0x00007fb0ae38475e n/a
(liboctinterp.so.4)
#3 0x00007fb0abb0f6f0
__restore_rt (libc.so.6)
#4 0x00007fb0ae2557cf n/a
(liboctinterp.so.4)
#5 0x00007fb0ae258778
_Z16dump_octave_corev (liboctinterp.so.4)
#6 0x00007fb0ae3846a3 n/a
(liboctinterp.so.4)
#7 0x00007fb0abb0f6f0
__restore_rt (libc.so.6)
#8 0x00007fb0abb0f670 raise
(libc.so.6)
#9 0x00007fb0abb10d00 abort
(libc.so.6)
#10 0x00007fb0a9c78807
_ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
#11 0x00007fb0a9c8777d
_ZN7QThreadD2Ev (libQt5Core.so.5)
#12 0x00007fb0a9c87859
_ZN7QThreadD0Ev (libQt5Core.so.5)
#13 0x00007fb0aea17611
_ZN14octave_qt_linkD1Ev (liboctgui.so.2)
#14 0x00007fb0aea176b9
_ZN14octave_qt_linkD0Ev (liboctgui.so.2)
#15 0x00007fb0aea0d410
_ZN11main_windowD1Ev (liboctgui.so.2)
#16 0x00007fb0aea16a76
_ZN6octave15gui_application7executeEv (liboctgui.so.2)
#17 0x00000000004010d8 n/a
(octave-gui)
#18 0x00007fb0abafc43a
__libc_start_main (libc.so.6)
#19 0x000000000040142a n/a
(octave-gui)
Stack trace of thread 28185:
#0 0x00007fb0abbbf24d poll
(libc.so.6)
#1 0x00007fb0a17bbbf9 n/a
(libglib-2.0.so.0)
#2 0x00007fb0a17bbd0c
g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fb0a9ebfe7f
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#4 0x00007fb0a9e6621a
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5 0x00007fb0a9c8840a
_ZN7QThread4execEv (libQt5Core.so.5)
#6 0x00007fb097c19d45 n/a
(libQt5DBus.so.5)
#7 0x00007fb0a9c8ccbd n/a
(libQt5Core.so.5)
#8 0x00007fb0a885b297
start_thread (libpthread.so.0)
#9 0x00007fb0abbc91ef
__clone (libc.so.6)
Stack trace of thread 28183:
#0 0x00007fb0abbbf24d poll
(libc.so.6)
#1 0x00007fb09fb598e0 n/a
(libxcb.so.1)
#2 0x00007fb09fb5b679
xcb_wait_for_event (libxcb.so.1)
#3 0x00007fb0980cbd49 n/a
(libQt5XcbQpa.so.5)
#4 0x00007fb0a9c8ccbd n/a
(libQt5Core.so.5)
#5 0x00007fb0a885b297
start_thread (libpthread.so.0)
#6 0x00007fb0abbc91ef
__clone (libc.so.6)
Stack trace of thread 28184:
#0 0x00007fb0abbbf24d poll
(libc.so.6)
#1 0x00007fb0a17bbbf9 n/a
(libglib-2.0.so.0)
#2 0x00007fb0a17bbd0c
g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fb0a9ebfe7f
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#4 0x00007fb0a9e6621a
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5 0x00007fb0a9c8840a
_ZN7QThread4execEv (libQt5Core.so.5)
#6 0x00007fb0a9c8ccbd n/a
(libQt5Core.so.5)
#7 0x00007fb0a885b297
start_thread (libpthread.so.0)
#8 0x00007fb0abbc91ef
__clone (libc.so.6)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51413>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |