public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-17300-4717-iEQuVlqgi3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17300-4717@http.sourceware.org/bugzilla/>
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.
next prev parent reply other threads:[~2014-10-07 11:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 4:11 [Bug cli/17300] New: " dilyan.palauzov at aegee dot org
2014-10-05 14:13 ` [Bug cli/17300] " jan.kratochvil at redhat dot com
2014-10-06 13:10 ` palves at redhat dot com
2014-10-06 13:12 ` palves at redhat dot com
2014-10-06 13:22 ` palves at redhat dot com
2014-10-07 11:32 ` dilyan.palauzov at aegee dot org [this message]
2014-10-07 15:37 ` palves at redhat dot com
2014-10-07 15:43 ` palves at redhat dot com
2014-10-09 15:51 ` palves at redhat dot com
2014-10-17 12:47 ` cvs-commit at gcc dot gnu.org
2014-10-17 13:30 ` palves at redhat dot com
2014-10-17 13:31 ` palves at redhat dot com
2014-10-18 11:51 ` dilyan.palauzov at aegee dot org
2014-10-24 18:10 ` palves at redhat dot com
2014-10-25 11:15 ` dilyan.palauzov at aegee dot org
2014-10-29 19:48 ` cvs-commit at gcc dot gnu.org
2014-12-25 0:46 ` cvs-commit at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-17300-4717-iEQuVlqgi3@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).