From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-16791-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 14307 invoked by alias); 7 Oct 2014 11:32:02 -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 14277 invoked by uid 48); 7 Oct 2014 11:32:01 -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: Tue, 07 Oct 2014 11:32: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: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-17300-4717-iEQuVlqgi3@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/msg00034.txt.bz2

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

--- Comment #5 from dilyan.palauzov at aegee dot org <dilyan.palauzov at aegee dot org> ---
Here is something I experience from time to time with GDB 7.8, that might be
related, but I cannot yet write the exact steps how to reproduce it:

In non-stop mode I attach& to a process, then do continue -a &, interrupt -a&
in chaotic way and while GDB doesn't crash, the debugged application crashes.

This might be also related to Bug 16809 (interrupt -a leads to GDB crash in
libreadline).  In particular, while before fixing Bug 16809 GDB crashed and the
application continued running, now GDB does not crash and the debugged
application aborts.

Anyway, the commands "interrupt -a&" and "continue -a&" may non repeat by
pressing <RET> in non-stop mode and this has to be written in the
documentation.

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