From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-16851-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 21797 invoked by alias); 18 Oct 2014 11:51:38 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Received: (qmail 21773 invoked by uid 48); 18 Oct 2014 11:51:37 -0000
From: "dilyan.palauzov at aegee dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/17300] crash in non-stop mode with continue -a &
 (readline_callback_read_char() called with no handler!)
Date: Sat, 18 Oct 2014 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: cli
X-Bugzilla-Version: 7.8
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dilyan.palauzov at aegee dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: palves at redhat dot com
X-Bugzilla-Target-Milestone: 7.9
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-17300-4717-1wyipI13FY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17300-4717@http.sourceware.org/bugzilla/>
References: <bug-17300-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q4/txt/msg00094.txt.bz2

https://sourceware.org/bugzilla/show_bug.cgi?id=17300

dilyan.palauzov at aegee dot org <dilyan.palauzov at aegee dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #13 from dilyan.palauzov at aegee dot org <dilyan.palauzov at aegee dot org> ---
To my understanding, all commands which do not repeat by pressing subsequent
<RET> are mentioned as such explicitly in the documentation.

There is no point to repeat "continue -a&" on subsequent <RET> when the program
is already running.

Please clarify in the documentation, that continue -a (and interrupt -a) do not
repeat, when the program with all its threads is running by the time <RET> is
pressed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.