From: Simon Marchi <simark@simark.ca>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't drop static function bp locations w/o debug info
Date: Fri, 12 Jun 2020 15:53:37 -0400 [thread overview]
Message-ID: <22959b69-54bd-012e-4026-feb4f02ac671@simark.ca> (raw)
In-Reply-To: <20200612192108.11481-1-pedro@palves.net>
On 2020-06-12 3:21 p.m., Pedro Alves wrote:
> @@ -4371,21 +4336,54 @@ search_minsyms_for_name (struct collect_info *info,
>
> if (!minsyms.empty ())
You could remove this check and de-indent the rest. If minsyms is empty, the loop
will just be skipped over.
Otherwise, LGTM.
Simon
next prev parent reply other threads:[~2020-06-12 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 19:21 Pedro Alves
2020-06-12 19:53 ` Simon Marchi [this message]
2020-09-13 13:25 ` Pedro Alves
2020-09-22 20:20 ` Luis Machado
2020-09-24 15:16 ` Pedro Alves
2020-09-24 15:32 ` Luis Machado
2020-09-24 15:35 ` Pedro Alves
2020-09-24 15:44 ` Luis Machado
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=22959b69-54bd-012e-4026-feb4f02ac671@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).