From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 0/3] Handle dynamic properties and static link
Date: Wed, 29 Mar 2023 10:16:17 -0600 [thread overview]
Message-ID: <87v8ijbkj2.fsf@tromey.com> (raw)
In-Reply-To: <20230309-submit-static-link-fix-v1-0-23af27781fd2@adacore.com> (Tom Tromey via Gdb-patches's message of "Thu, 09 Mar 2023 10:50:54 -0700")
>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> Ada uses static links and dynamic properties more than most other
Tom> languages. A user found a bug when the two are combined, and this
Tom> series fixes the problem.
Tom> Regression tested on x86-64 Fedora 36.
I'm checking this in now.
Tom
prev parent reply other threads:[~2023-03-29 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 17:50 Tom Tromey
2023-03-09 17:50 ` [PATCH 1/3] Add frame parameter to resolve_dynamic_type Tom Tromey
2023-03-09 17:50 ` [PATCH 2/3] Pass a frame to value_at_lazy and value_from_contents_and_address Tom Tromey
2023-03-09 17:50 ` [PATCH 3/3] Use the correct frame when evaluating a dynamic property Tom Tromey
2023-03-29 16:16 ` Tom Tromey [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=87v8ijbkj2.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@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).