|
| From: | Mike Miller |
| Subject: | [Octave-bug-tracker] [bug #47326] segfault in GUI and interpreter initialization |
| Date: | Thu, 03 Mar 2016 00:05:43 +0000 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Iceweasel/44.0.2 |
URL:
<http://savannah.gnu.org/bugs/?47326>
Summary: segfault in GUI and interpreter initialization
Project: GNU Octave
Submitted by: mtmiller
Submitted on: Wed 02 Mar 2016 04:05:42 PM PST
Category: GUI
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Crash
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: GNU/Linux
_______________________________________________________
Details:
I'm seeing a sporadic segfault when Octave's GUI starts up.
The attached contains a gdb backtrace of the two threads showing that they are
both in initialization routines.
I got this by running the following shell loop:
rm -f core
ulimit -c unlimited
while ! [ -f core ]; do
./run-octave -qfH /dev/null
done
Runs for a few minutes before a segfault occurs.
I'll try messing with my environment to make sure it's not something about my
configuration causing this.
This is what leads to a segfault when building doc/interpreter for me
occasionally. I don't see the crash at all with octave-cli.
_______________________________________________________
File Attachments:
-------------------------------------------------------
Date: Wed 02 Mar 2016 04:05:42 PM PST Name: bt.txt Size: 7kB By: mtmiller
<http://savannah.gnu.org/bugs/download.php?file_id=36532>
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47326>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |