Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Matt Rice <ratmice@gmail.com>
Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch] [python] find_line_pc_range
Date: Mon, 04 Jul 2011 13:14:00 -0000	[thread overview]
Message-ID: <E1Qdhu9-0001Bt-9i@fencepost.gnu.org> (raw)
In-Reply-To: <CACTLOFqppKbUTP7NMauBXJKy+3ptuKzETzU5Ds6Zad1uBvHoVg@mail.gmail.com>	(message from Matt Rice on Mon, 4 Jul 2011 03:50:11 -0700)

> Date: Mon, 4 Jul 2011 03:50:11 -0700
> From: Matt Rice <ratmice@gmail.com>
> Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org
> 
> >> +@defmethod Symtab_and_line find_line_pc_range
> >> +If found returns a @code{Tuple} containing the start and end program counter
> >> +addresses for the line attribute.  Otherwise returns @code{None}.
> >
> > Sorry, I don't understand what you are trying to say here.
> >  "If found"
> > what?
> 
> Sorry, I abhor writing.
> find_line_pc_range will not find a range in cases where
> the code is not associated with a line (no debug symbols), or the line
> is not associated with code (ifdef'd out or something).
> 
> >  And what "line attribute" do you refer to?
> 
> this thing:
> — Instance Variable of Symtab_and_line: line
> 
> Indicates the current line number for this object. This attribute is
> not writable.

Thanks for explaining.  I would rephrase as follows:

  Attempt to find the range of program counter addresses for the
  @code{line} attribute of the @code{Symtab_and_line} object.  If
  found, return a @code{Tuple} containing the start and end addresses
  for the line.  Otherwise (e.g., a line with no corresponding code or
  not present in the debug info), return @code{None}.


      reply	other threads:[~2011-07-04 12:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02  4:03 Matt Rice
2011-07-03 16:35 ` Phil Muldoon
2011-07-04  5:38   ` Phil Muldoon
2011-07-04  6:36   ` Matt Rice
2011-07-04 10:09     ` Phil Muldoon
2011-07-05  2:47       ` Matt Rice
2011-07-05 20:41         ` Phil Muldoon
2011-07-04 10:50     ` Eli Zaretskii
2011-07-04 10:56       ` Matt Rice
2011-07-04 13:14         ` Eli Zaretskii [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=E1Qdhu9-0001Bt-9i@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@redhat.com \
    --cc=ratmice@gmail.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