Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] python: Add qualified parameter to gdb.Breakpoint
Date: Wed, 13 Dec 2017 13:17:00 -0000	[thread overview]
Message-ID: <2c2971c3-dd3f-1c92-4a8f-60c69aea65cf@redhat.com> (raw)
In-Reply-To: <7f59352579a659f3ee96f6a9e5404f9b@polymtl.ca>

On 12/08/2017 06:42 PM, Simon Marchi wrote:

>> So we either need to clarify that in the Python bits too,
>> or some do some xref'ing.
> 
> Agreed, I didn't like that wording either.  I had only found the
> Linespec Locations page, which doesn't specifically say "fully-qualified
> name", but mentions free-function (though it's in an example, not a
> formal definition).  How is this?
> 
> The optional @var{qualified} argument is a boolean that allows interpreting
> the function passed in @code{spec} as a fully-qualified name.  It is
> equivalent
> to @code{break}'s @code{-qualified} flag (@pxref{Linespec Locations} and
> @ref{Explicit Locations}).

Thanks, that looks fine.

(I thought I had replied earlier, but looks like I dreamt it.)

Thanks,
Pedro Alves


  reply	other threads:[~2017-12-13 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 22:34 Simon Marchi
2017-12-08 12:05 ` Pedro Alves
2017-12-08 18:42   ` Simon Marchi
2017-12-13 13:17     ` Pedro Alves [this message]
2017-12-13 16:45       ` Simon Marchi
2017-12-08 14:15 ` Eli Zaretskii
2017-12-08 18:27   ` Simon Marchi
2017-12-08 19:47     ` Eli Zaretskii

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=2c2971c3-dd3f-1c92-4a8f-60c69aea65cf@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.com \
    --cc=simon.marchi@polymtl.ca \
    /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