public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "zbigniew2011 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30872] Assertion `buffer.copy_insn_closure.get () != nullptr' failed
Date: Tue, 19 Sep 2023 12:02:25 +0000	[thread overview]
Message-ID: <bug-30872-4717-G7ZO6MpAxy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30872-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Zbigniew <zbigniew2011 at gmail dot com> ---
Just imagine: this bug DOESN'T occur in old version 10.1. Just a few minutes
ago I verified it using old package (GNU gdb (Debian 10.1-1.7)
10.1.90.20210103-git).

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

  reply	other threads:[~2023-09-19 12:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  9:43 [Bug gdb/30872] New: " zbigniew2011 at gmail dot com
2023-09-19 12:02 ` zbigniew2011 at gmail dot com [this message]
2023-09-19 12:29 ` [Bug gdb/30872] " tromey at sourceware dot org
2023-09-19 12:34 ` zbigniew2011 at gmail dot com
2023-09-19 16:02 ` ssbssa at sourceware dot org
2023-09-19 18:00 ` tromey at sourceware dot org
2023-09-19 20:31 ` luis.machado at arm dot com
2023-09-27 11:46 ` luis.machado at arm dot com
2023-09-27 12:39 ` luis.machado at arm dot com
2023-09-27 13:27 ` zbigniew2011 at gmail dot com
2023-09-27 14:07 ` luis.machado at arm dot com
2023-09-28  8:13 ` luis.machado at arm dot com
2023-09-28 10:50 ` sam at gentoo dot org
2023-09-29  8:16 ` luis.machado at arm dot com
2023-10-16 10:57 ` cvs-commit at gcc dot gnu.org
2023-10-16 10:59 ` cvs-commit at gcc dot gnu.org
2023-10-16 11:01 ` luis.machado at arm dot com

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-30872-4717-G7ZO6MpAxy@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).