From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH master + 11][gdb/symtab] Fix zero address complaint for shlib
Date: Fri, 30 Jul 2021 13:50:18 -0400 [thread overview]
Message-ID: <8e1b2a6e-dedb-3184-713f-381c8b51be0b@polymtl.ca> (raw)
In-Reply-To: <b00ce629-a676-530d-9c18-684ccfde5c27@suse.de>
> Thanks for the review, and the .debug_rnglists addition.
>
> I've added the .debug_rnglists addition here as well, and added testing
> the complaint when doing gdb_load $lib1, in other words, the unrelocated
> case (which was already passing before this patch).
Thanks, this LGTM.
Note, when merging in master, you can use the Co-Authored-By tag, since
we don't have a ChangeLog file there.
Simon
next prev parent reply other threads:[~2021-07-30 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 21:23 Tom de Vries
2021-07-30 1:25 ` Simon Marchi via Gdb-patches
2021-07-30 1:48 ` Simon Marchi via Gdb-patches
2021-07-30 15:25 ` Tom de Vries
2021-07-30 17:50 ` Simon Marchi via Gdb-patches [this message]
2021-08-01 17:59 ` Tom de Vries
2021-08-02 13:09 ` Simon Marchi via Gdb-patches
2021-08-06 14:43 ` Tom de Vries 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=8e1b2a6e-dedb-3184-713f-381c8b51be0b@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
/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