[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #54932] Segfault when starting GUI with -q
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #54932] Segfault when starting GUI with -q |
Date: |
Thu, 1 Nov 2018 12:14:33 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 |
URL:
<https://savannah.gnu.org/bugs/?54932>
Summary: Segfault when starting GUI with -q
Project: GNU Octave
Submitted by: rik5
Submitted on: Thu 01 Nov 2018 09:14:31 AM PDT
Category: GUI
Severity: 5 - Blocker
Priority: 5 - Normal
Item Group: Regression
Status: Confirmed
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Any
_______________________________________________________
Details:
On the dev branch, start Octave with
./run-octave -f -q --gui
Next, click on the Command Window and Octave segfaults.
Using hg bisect, this behavior was introduced in this cset
parent: 25988:976e7346abf4
Make gui command line mouse compatible for non-windows systems (bug #45003)
branch: default
The problem seems to be that when '-q' is used there are no lines in the
Command Window and so some count is either zero, or goes negative. Without
'-q', Octave prints some generic help info which at least places something in
the Command Window buffer.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?54932>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #54932] Segfault when starting GUI with -q,
Rik <=