public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "guillaume at morinfr dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/27889] jit.c:1178: internal-error: void jit_event_handler(gdbarch*, objfile*): Assertion `jiter->jiter_data != nullptr' failed.
Date: Thu, 23 Jun 2022 13:36:07 +0000 [thread overview]
Message-ID: <bug-27889-4717-aNBJyRFWwk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27889-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27889
--- Comment #11 from Guillaume Morin <guillaume at morinfr dot org> ---
Hi Tom, as you guessed, yes we've hit the same assert but this is not the same
bug. We've opened a new PR:
https://sourceware.org/bugzilla/show_bug.cgi?id=29277
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-06-23 13:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 10:03 [Bug gdb/27889] New: " vries at gcc dot gnu.org
2021-05-20 10:08 ` [Bug gdb/27889] " vries at gcc dot gnu.org
2021-05-20 10:40 ` vries at gcc dot gnu.org
2021-05-20 11:34 ` pafee at tycoint dot com
2021-05-20 12:10 ` vries at gcc dot gnu.org
2021-05-20 13:23 ` [Bug breakpoints/27889] " vries at gcc dot gnu.org
2021-05-20 13:32 ` vries at gcc dot gnu.org
2021-05-20 13:36 ` vries at gcc dot gnu.org
2021-05-20 15:30 ` vries at gcc dot gnu.org
2021-05-21 13:09 ` cvs-commit at gcc dot gnu.org
2021-05-21 13:19 ` vries at gcc dot gnu.org
2022-06-22 19:08 ` hector.oron at gmail dot com
2022-06-22 19:10 ` hector.oron at gmail dot com
2022-06-22 19:13 ` guillaume at morinfr dot org
2022-06-23 12:20 ` vries at gcc dot gnu.org
2022-06-23 13:36 ` guillaume at morinfr dot org [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-27889-4717-aNBJyRFWwk@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).