public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/27927] gdb crash with OpenOCD
Date: Thu, 09 Feb 2023 21:45:16 +0000 [thread overview]
Message-ID: <bug-27927-4717-WQdlUa7d64@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27927-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27927
--- Comment #17 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Jérôme Pouiller from comment #16)
> BTW, I believe gdb shouldn't crash even when the remote is buggy.
Yeah, totally agreed.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-02-09 21:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 12:47 [Bug remote/27927] New: " jerome.pouiller at gmail dot com
2021-05-28 12:49 ` [Bug remote/27927] " jerome.pouiller at gmail dot com
2021-05-28 12:52 ` jerome.pouiller at gmail dot com
2021-05-28 13:40 ` simark at simark dot ca
2021-06-01 8:14 ` jerome.pouiller at gmail dot com
2021-06-01 8:21 ` jerome.pouiller at gmail dot com
2021-06-01 8:23 ` jerome.pouiller at gmail dot com
2021-06-01 13:43 ` simark at simark dot ca
2021-06-01 13:44 ` simark at simark dot ca
2021-06-02 6:22 ` alucca388 at gmail dot com
2021-06-02 7:06 ` jerome.pouiller at gmail dot com
2021-06-02 7:26 ` jerome.pouiller at gmail dot com
2021-06-02 7:29 ` jerome.pouiller at gmail dot com
2021-06-02 13:28 ` simark at simark dot ca
2021-11-06 9:04 ` fredrik.hederstierna@securitas-direct.com
2022-06-29 13:43 ` robertjenssen at ozemail dot com.au
2023-01-17 16:28 ` tromey at sourceware dot org
2023-02-09 14:40 ` jerome.pouiller at gmail dot com
2023-02-09 14:43 ` jerome.pouiller at gmail dot com
2023-02-09 21:45 ` tromey at sourceware dot org [this message]
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-27927-4717-WQdlUa7d64@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).