From: Pedro Alves <palves@redhat.com>
To: Shahab Vahedi <shahab.vahedi@gmail.com>
Cc: gdb-patches@sourceware.org, Shahab Vahedi <shahab@synopsys.com>,
Claudiu Zissulescu <claziss@synopsys.com>,
Francois Bedard <fbedard@synopsys.com>
Subject: Re: [PATCH v2] GDB: Fix the overflow in addr_is_displayed()
Date: Mon, 06 Jan 2020 13:03:00 -0000 [thread overview]
Message-ID: <45a718f7-e905-e7b1-1596-6ef6c4204176@redhat.com> (raw)
In-Reply-To: <20200106124353.GB1101@gmail.com>
On 1/6/20 12:43 PM, Shahab Vahedi wrote:
> How does this look?
>
> bool is_displayed = false;
> int threshold = SCROLL_THRESHOLD;
>
> - int i = 0;
> - while (i < content.size () - threshold && !is_displayed)
> + if (content.size () < threshold)
> + return is_displayed;
> +
I'd write "false" instead of "is_displayed", to remove the
indirection. Actually, do we really need the "threshold"
variable, btw? Or even, "is_displayed"? Isn't the
following equivalent?
if (content.size () < SCROLL_THRESHOLD)
return false;
for (size_t i = 0;
i < content.size () - SCROLL_THRESHOLD;
i++)
{
if (content[i].line_or_addr.loa == LOA_ADDRESS
&& content[i].line_or_addr.u.addr == addr)
return true;
}
return false;
Anyway, what you have is fine too.
More importantly, doesn't tui_source_window::line_is_displayed
have the exact same issue?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2020-01-06 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200106102649.15710-1-shahab.vahedi@gmail.com>
2020-01-06 12:18 ` Pedro Alves
2020-01-06 12:43 ` Shahab Vahedi
2020-01-06 13:03 ` Pedro Alves [this message]
2020-01-06 14:27 ` [PATCH v3] GDB: Fix the overflow in addr/line_is_displayed() Shahab Vahedi
2020-01-06 19:55 ` Pedro Alves
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=45a718f7-e905-e7b1-1596-6ef6c4204176@redhat.com \
--to=palves@redhat.com \
--cc=claziss@synopsys.com \
--cc=fbedard@synopsys.com \
--cc=gdb-patches@sourceware.org \
--cc=shahab.vahedi@gmail.com \
--cc=shahab@synopsys.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