public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Omair Javaid <omair.javaid@linaro.org>
To: Tom Tromey <tom@tromey.com>
Cc: simon.marchi@polymtl.ca, GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [PR gdb/21695] Fix lost line info for symbol at addr zero
Date: Mon, 25 Jun 2018 10:11:00 -0000	[thread overview]
Message-ID: <CANW4E-38k_yFCGnNVgB5VXnkE==m+TQVOBcrD5c1cJrgy4w1MQ@mail.gmail.com> (raw)
In-Reply-To: <87602cov18.fsf@tromey.com>

On Thu, 21 Jun 2018 at 23:26, Tom Tromey <tom@tromey.com> wrote:
>
> >>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
>
> Simon> I have added Tom Tromey in CC, he is currently playing with storing
> Simon> symbols relocated vs unrelocated, so maybe he knows better.  And maybe
> Simon> there's something in his pending patches that also touch this area.
>
> The patch seems reasonable to me.
>
> I think it may touch the same code as my line table series, but that's
> no big deal.  I'll rebase when the time comes.
>
> >> +                                   CORE_ADDR lowpc_minus_base, CORE_ADDR address)
>
> Simon> I would suggest naming this "unrelocated_lowpc".  Can you update the
> Simon> documentation of the method to describe that parameter?
>
> Agreed.
>
> >> /* If address < lowpc then it's not a usable value, it's outside the
> >> pc range of the CU.  However, we restrict the test to only
>
> This comment could also use an update, and it should be using upper-case
> like "ADDRESS" and "LOWPC".
>
> Tom
Thanks Tom and Simon for review. I will send an update after fixing
highlighted issues.

      reply	other threads:[~2018-06-25 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 14:56 Omair Javaid
2018-05-28 12:36 ` Omair Javaid
2018-06-12  2:26   ` Omair Javaid
2018-06-20  7:53     ` Omair Javaid
2018-06-20 16:12 ` Simon Marchi
2018-06-21 18:27   ` Tom Tromey
2018-06-25 10:11     ` Omair Javaid [this message]

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='CANW4E-38k_yFCGnNVgB5VXnkE==m+TQVOBcrD5c1cJrgy4w1MQ@mail.gmail.com' \
    --to=omair.javaid@linaro.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).