public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dmitry.neverov at jetbrains dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31727] -exec-next fails in mingw (infrun.c:2794: internal-error: resume_1: Assertion `pc_in_thread_step_range (pc, tp)' failed)
Date: Wed, 22 May 2024 13:42:36 +0000	[thread overview]
Message-ID: <bug-31727-4717-6fQX6Ev4yG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31727-4717@http.sourceware.org/bugzilla/>

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

--- Comment #6 from Dmitry Neverov <dmitry.neverov at jetbrains dot com> ---
Created attachment 15530
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15530&action=edit
gdb-14.2 stepping log (crashes)

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

  parent reply	other threads:[~2024-05-22 13:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10 15:50 [Bug gdb/31727] New: " dmitry.neverov at jetbrains dot com
2024-05-10 17:41 ` [Bug gdb/31727] " dmitry.neverov at jetbrains dot com
2024-05-18 11:24 ` ssbssa at sourceware dot org
2024-05-21 14:19 ` dmitry.neverov at jetbrains dot com
2024-05-21 16:38 ` simon.marchi at polymtl dot ca
2024-05-22 13:42 ` dmitry.neverov at jetbrains dot com
2024-05-22 13:42 ` dmitry.neverov at jetbrains dot com [this message]
2024-05-22 13:43 ` dmitry.neverov at jetbrains dot com
2024-05-24  8:42 ` dmitry.neverov at jetbrains dot com
2024-05-24 15:47 ` tromey at sourceware dot org
2024-05-26 16:08 ` dmitry.neverov at jetbrains dot com
2024-05-28 18:24 ` tromey at sourceware dot org
2024-05-28 18:46 ` tromey at sourceware dot org
2024-05-28 19:02 ` tromey at sourceware dot org
2024-06-05  8:51 ` dmitry.neverov at jetbrains dot com
2024-06-05  9:35 ` dmitry.neverov at jetbrains dot com
2024-06-05 18:25 ` tromey at sourceware dot org
2024-06-06  7:10 ` dmitry.neverov at jetbrains dot com
2024-06-07 21:37 ` tromey at sourceware dot org

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-31727-4717-6fQX6Ev4yG@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).