From: Simon Marchi <simark@simark.ca>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Cc: Eli Zaretskii <eliz@gnu.org>, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCHv3] gdb: add Python events for program space addition and removal
Date: Mon, 2 Oct 2023 16:38:54 -0400 [thread overview]
Message-ID: <7aced4dc-72db-4e91-9644-bd8d611a0970@simark.ca> (raw)
In-Reply-To: <87a5t0yd62.fsf@redhat.com>
> Thanks for bringing this to my attention. I was sure I'd tested this on
> all boards (I've been trying to make use of make-check-all.sh lately),
> but I guess I messed up here :-/
>
> I will 100% look into this issue, however, it's worth nothing that this
> is not something my patch broke, it's just my test exposed this issue,
> which is a regression since GDB 13.
>
> I say this only in case anyone else has any thoughts.
>
> I will pick this up tomorrow to investigate.
I have not investigated more than that, so I'm not sure which regression
you are referring to. Do you mean something worked in GDB 13 and
doesn't in current master? If so, it would be worth filing a bug (if
there isn't already) and informing Joel that this might be a blocker for
the release (not necessarily the branching).
Simon
next prev parent reply other threads:[~2023-10-02 20:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 12:44 [PATCH] " Andrew Burgess
2023-09-21 19:20 ` Tom Tromey
2023-09-27 10:51 ` Andrew Burgess
2023-09-27 14:20 ` Tom Tromey
2023-09-27 15:17 ` Andrew Burgess
2023-09-27 15:16 ` [PATCHv2] " Andrew Burgess
2023-09-29 12:41 ` Eli Zaretskii
2023-09-29 13:24 ` [PATCHv3] " Andrew Burgess
2023-09-29 15:46 ` Eli Zaretskii
2023-10-02 16:09 ` Andrew Burgess
2023-10-02 18:34 ` Simon Marchi
2023-10-02 20:36 ` Andrew Burgess
2023-10-02 20:38 ` Simon Marchi [this message]
2023-10-02 21:17 ` Andrew Burgess
2023-10-02 20:11 ` [PUSHED] gdb/python: reformat file with black Andrew Burgess
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=7aced4dc-72db-4e91-9644-bd8d611a0970@simark.ca \
--to=simark@simark.ca \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).