public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/15275] gdb quit command fails if remote serial link is broken
Date: Mon, 25 Mar 2013 19:59:00 -0000 [thread overview]
Message-ID: <bug-15275-4717-BgAhhLB989@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15275-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15275
Jan Kratochvil <jan.kratochvil at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #4 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2013-03-25 19:59:05 UTC ---
Valid bugreport, as verified in:
http://sourceware.org/ml/gdb-patches/2013-03/msg00948.html
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-03-25 19:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 23:51 [Bug remote/15275] New: " gareth at blacksphere dot co.nz
2013-03-13 23:54 ` [Bug remote/15275] " gareth at blacksphere dot co.nz
2013-03-14 1:13 ` gareth at blacksphere dot co.nz
2013-03-14 1:32 ` gareth at blacksphere dot co.nz
2013-03-20 17:09 ` jan.kratochvil at redhat dot com
2013-03-25 19:59 ` jan.kratochvil at redhat dot com [this message]
2013-03-27 18:20 ` cvs-commit at gcc dot gnu.org
2013-03-27 18:21 ` cvs-commit at gcc dot gnu.org
2013-03-27 18:23 ` jan.kratochvil at redhat dot com
2013-04-02 13:51 ` cvs-commit at gcc dot gnu.org
2013-04-02 13:54 ` cvs-commit at gcc dot gnu.org
2013-04-02 14:09 ` cvs-commit at gcc dot gnu.org
2013-04-02 14:11 ` cvs-commit at gcc dot gnu.org
2013-04-10 14:10 ` 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-15275-4717-BgAhhLB989@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).