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 gdb/27317] gdb crashes upon target remote :1234
Date: Sun, 06 Mar 2022 17:41:09 +0000 [thread overview]
Message-ID: <bug-27317-4717-zY7CQdCWeP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27317-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27317
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
Last reconfirmed| |2022-03-06
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
A core dump of gdb isn't super useful, because it's specific
to your build of gdb. The failing executable might be useful
if the problem can be reproduced without any special setup
(maybe not in this case). A stack trace from gdb itself might
also be informative.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-03-06 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 17:26 [Bug gdb/27317] New: " r.kloos at campus dot tu-berlin.de
2021-02-02 17:29 ` [Bug gdb/27317] " r.kloos at campus dot tu-berlin.de
2021-02-02 17:30 ` r.kloos at campus dot tu-berlin.de
2022-03-06 17:41 ` tromey at sourceware dot org [this message]
2022-03-06 18:26 ` r.kloos at campus dot tu-berlin.de
2022-03-06 18:30 ` r.kloos at campus dot tu-berlin.de
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-27317-4717-zY7CQdCWeP@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).