public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/28906] GDB debugger hangs after step call
Date: Fri, 18 Feb 2022 14:20:48 +0000	[thread overview]
Message-ID: <bug-28906-4717-29fzjhgEd4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28906-4717@http.sourceware.org/bugzilla/>

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

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simark at simark dot ca

--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
Hi,

Can you please test with GDB master, or at least the latest released version
(11.2)?

When you do so, please enable "set debug infrun 1" just before your step.  It
will help whoever investigates this bug.

Simon

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

  parent reply	other threads:[~2022-02-18 14:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 14:07 [Bug c++/28906] New: " aakash0641 at gmail dot com
2022-02-18 14:07 ` [Bug c++/28906] " aakash0641 at gmail dot com
2022-02-18 14:10 ` aakash0641 at gmail dot com
2022-02-18 14:20 ` simark at simark dot ca [this message]
2022-02-18 15:18 ` aakash0641 at gmail dot com
2022-02-18 15:23 ` simark at simark dot ca
2022-02-18 16:16 ` aakash0641 at gmail dot com
2022-02-18 16:26 ` simark at simark dot 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-28906-4717-29fzjhgEd4@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).