From: Simon Marchi <simon.marchi@polymtl.ca>
To: Jan Vrany <jan.vrany@labware.com>,
Simon Marchi <simark@simark.ca>,
gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: Re: [pushed] gdb/mi: consistently notify user when GDB/MI client uses -thread-select
Date: Thu, 24 Mar 2022 11:00:12 -0400 [thread overview]
Message-ID: <3d099d31-e444-6693-a151-481da8e438c0@polymtl.ca> (raw)
In-Reply-To: <e7517ece8f9ca7540bc228f960dc55afc8cf226f.camel@labware.com>
On 2022-03-23 12:09, Jan Vrany wrote:
> Thanks! Now it is failing for me too!
> I just recompiled GDB using the above command. I'll have a
> look tomorrow.
>
> Jan
Probably because of ASan? I initially ruled that out, because it's not
an ASan crash. But it's possible that it is impacting memory
allocation, such that the old and new frame_info objects are allocated
at different places.
Glad there was an actual bug and I was not crazy!
Simon
prev parent reply other threads:[~2022-03-24 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 15:09 Jan Vrany
2022-03-21 20:35 ` Simon Marchi
2022-03-21 21:01 ` Jan Vrany
2022-03-22 14:37 ` Jan Vrany
2022-03-23 12:36 ` Simon Marchi
2022-03-23 15:13 ` Jan Vrany
2022-03-23 15:16 ` Simon Marchi
2022-03-23 16:09 ` Jan Vrany
2022-03-23 19:09 ` Andrew Burgess
2022-03-23 19:11 ` Andrew Burgess
2022-03-23 20:33 ` Jan Vrany
2022-03-24 14:47 ` Simon Marchi
2022-03-24 18:52 ` [PATCHv2] gdb/mi: fix use after free of frame_info causing spurious notifications Andrew Burgess
2022-03-24 20:32 ` Simon Marchi
2022-03-29 10:10 ` Andrew Burgess
2022-03-24 15:00 ` Simon Marchi [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=3d099d31-e444-6693-a151-481da8e438c0@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.vrany@labware.com \
--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).