From: Jan Vrany <jan.vrany@labware.com>
To: Simon Marchi <simark@simark.ca>, GDB mailing list <gdb@sourceware.org>
Subject: Re: GDB crashes when using GDB/MI and python pretty printers in some cases
Date: Tue, 22 Mar 2022 12:31:04 +0000 [thread overview]
Message-ID: <679ec2bf4773824b99b24979a90ed0673646b077.camel@labware.com> (raw)
In-Reply-To: <fc3d4755-7f04-903b-a88a-a6da06d55de7@simark.ca>
On Fri, 2022-03-18 at 11:57 -0400, Simon Marchi wrote:
> On 2022-03-17 09:29, Jan Vrany via Gdb wrote:
> > Hi Simon, others,
> >
> > TL;DR:
> >
> > I'm experiencing GDB crashes with recent GDB which seem to be
> > caused by commit 5f8ab46. Why is that I do not know (yet). Some
> > details below.
> >
> > Full story:
> >
...
> >
> > I'll try to investigate further when I find more time, but in case someone brave
> > enough to read through this post has an idea, I'll appreciate it!
> >
> > Thanks, Jan
>
> Can you file a bug? Even if you don't have a simple reproducer yet, that's fine, include
> the same info you gave above.
>
> Simon
Sure! https://sourceware.org/bugzilla/show_bug.cgi?id=28988
Jan
prev parent reply other threads:[~2022-03-22 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 13:29 Jan Vrany
2022-03-18 15:57 ` Simon Marchi
2022-03-22 12:31 ` Jan Vrany [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=679ec2bf4773824b99b24979a90ed0673646b077.camel@labware.com \
--to=jan.vrany@labware.com \
--cc=gdb@sourceware.org \
--cc=simark@simark.ca \
/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).