From: Shahab Vahedi <shahab.vahedi@gmail.com>
To: Pedro Alves <palves@redhat.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 12:43:00 -0000 [thread overview]
Message-ID: <20200106124353.GB1101@gmail.com> (raw)
In-Reply-To: <11035b53-bb43-740a-de38-6283062cdc6d@redhat.com>
On Mon, Jan 06, 2020 at 12:17:51PM +0000, Pedro Alves wrote:
> On 1/6/20 10:26 AM, Shahab Vahedi wrote:
> > From: Shahab Vahedi <shahab@synopsys.com>
> >
> > In a corner case scenario, where the height of the assembly TUI is
> > bigger than the number of instructions in the whole program, GDB
> > dumps core. The problem roots in this condition check:
> >
> > int i = 0;
> > while (i < content. size() - threshold ...) {
> > ... content[i] ...
> > }
> >
> > "threshold" is 2 and there are times that "content. size()" is 0.
>
> Typo: spurious space in "content. size()", twice. Should be "content.size ()"
> instead.
Indeed! Andrew mentioned the same to me. I will fix 'em.
>
> > This results into an overflow and the loop is entered whereas it
> > should have been skipped.
> >
> > This has been discussed at length in bug 25345:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=25345
> >
> > As a bonus, a few trailing spaces are also removed.
>
> We try to avoid mixing unrelated formatting changes with
> logical changes. It would be better to push the whitespace
> fixing as a separate patch. Go ahead and merge that part
> in as an obvious change.
I will submit the trailing spaces fix in a separate patch.
>
> > @@ -349,10 +349,10 @@ bool
> > tui_disasm_window::addr_is_displayed (CORE_ADDR addr) const
> > {
> > bool is_displayed = false;
> > - int threshold = SCROLL_THRESHOLD;
> > + int nr_of_lines = (int) content. size() - SCROLL_THRESHOLD;
> >
>
> Someone reading this will have to think through the reason for
> the int cast, since negative "number of lines" is a bit
> nonsensical. I suspect that instead doing an early return, like:
>
> if (content.size() < SCROLL_THRESHOLD)
> return false;
>
> would end up being clearer?
>
> That "while" loop could be a "for" too, no idea why it's not.
>
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;
+
+ for (size_t i = 0; i < content.size () - threshold && !is_displayed; ++i)
{
is_displayed
= (content[i].line_or_addr.loa == LOA_ADDRESS
&& content[i].line_or_addr.u.addr == addr);
- i++;
}
> Thanks,
> Pedro Alves
>
--
Shahab
next prev parent reply other threads:[~2020-01-06 12:43 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 [this message]
2020-01-06 13:03 ` Pedro Alves
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=20200106124353.GB1101@gmail.com \
--to=shahab.vahedi@gmail.com \
--cc=claziss@synopsys.com \
--cc=fbedard@synopsys.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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