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/30205] [qemu-gdbserver -- i386] Gdb crash while debugging the pintos kernel, some kind of readline issue?
Date: Tue, 07 Mar 2023 14:40:22 +0000	[thread overview]
Message-ID: <bug-30205-4717-ZCNNd5bHL2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30205-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30205

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
Thank you for the bug report.

I'm not sure there is really enough information here to diagnose it.
Lack of reproducibility may also be an issue.
Anyway, my first suggestion would be to build a '-g -O0' gdb in
order to get a more reliable stack trace if it does happen again.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-03-07 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  3:19 [Bug gdb/30205] New: " liam.naddell at mail dot utoronto.ca
2023-03-07  3:20 ` [Bug gdb/30205] " liam.naddell at mail dot utoronto.ca
2023-03-07  3:22 ` liam.naddell at mail dot utoronto.ca
2023-03-07  3:28 ` liam.naddell at mail dot utoronto.ca
2023-03-07 14:40 ` tromey at sourceware dot org [this message]
2023-03-08  0:43 ` liam.naddell at mail dot utoronto.ca

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-30205-4717-ZCNNd5bHL2@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).