public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "r.kloos at campus dot tu-berlin.de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27317] gdb crashes upon target remote :1234
Date: Sun, 06 Mar 2022 18:30:08 +0000 [thread overview]
Message-ID: <bug-27317-4717-KpDz4GkgQr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27317-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27317
--- Comment #5 from r.kloos at campus dot tu-berlin.de ---
(In reply to Tom Tromey from comment #3)
> 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.
Apart from the backtrace I could also upload the executable, but I am not sure
if it would be helpful without the rest of the code.
It's kernel code from a university course running on qemu, so reproducing the
bug would need a special setup software wise.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-03-06 18:30 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
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 [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-27317-4717-KpDz4GkgQr@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).