From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb: fix logic of find_comp_unit and set_comp_unit
Date: Thu, 03 Dec 2020 13:42:57 -0700 [thread overview]
Message-ID: <87h7p2aaem.fsf@tromey.com> (raw)
In-Reply-To: <20201203180011.1909405-1-simon.marchi@polymtl.ca> (Simon Marchi via Gdb-patches's message of "Thu, 3 Dec 2020 13:00:11 -0500")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> PR gdb/26876
Simon> * dwarf2/frame.c (find_comp_unit, set_comp_unit): Reverse use of
Simon> dwarf2_frame_bfd_data and dwarf2_frame_objfile_data.
This looks good to me. Thank you.
Tom
next prev parent reply other threads:[~2020-12-03 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 18:00 Simon Marchi via Gdb-patches
2020-12-03 20:42 ` Tom Tromey [this message]
2020-12-03 20:48 ` Simon Marchi via Gdb-patches
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=87h7p2aaem.fsf@tromey.com \
--to=tom@tromey.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