Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] py-breakpoint: Don't use the 'p' PyArg_ParseTupleAndKeywords format specifier
Date: Thu, 14 Dec 2017 20:48:00 -0000	[thread overview]
Message-ID: <ab9e6a453f30cfc886e01576354bdac5@polymtl.ca> (raw)
In-Reply-To: <1513281201-9279-1-git-send-email-simon.marchi@ericsson.com>

On 2017-12-14 14:53, Simon Marchi wrote:
> In Python 3, the 'p' format specifier can be passed to
> PyArg_ParseTupleAndKeywords to test the argument for truth and convert
> it to a boolean value (the p stands for predicate).  However, it is not
> available in Python 2, causing this error:
> 
>   Traceback (most recent call last):
>     File "test.py", line 1, in <module>
>       b1 = gdb.Breakpoint("foo", qualified=False)
>   TypeError: argument 10 (impossible<bad format char>)
> 
> This patch changes it to the 'O' specifier, which returns the Python
> object passed in without transformation, and uses PyObject_IsTrue on 
> it.
> This is what is done for the other boolean parameters of this function
> (internal and temporary).
> 
> This fixes the test gdb.python/py-breakpoint.exp for Python 2.
> 
> gdb/ChangeLog:
> 
> 	* python/py-breakpoint.c (bppy_init): Use 'O' format specifier
> 	for "qualified" and use PyObject_IsTrue.
> ---
>  gdb/python/py-breakpoint.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/gdb/python/py-breakpoint.c b/gdb/python/py-breakpoint.c
> index ce680c4..05291b5 100644
> --- a/gdb/python/py-breakpoint.c
> +++ b/gdb/python/py-breakpoint.c
> @@ -707,9 +707,9 @@ bppy_init (PyObject *self, PyObject *args, PyObject 
> *kwargs)
>    char *label = NULL;
>    char *source = NULL;
>    char *function = NULL;
> -  int qualified = 0;
> +  PyObject * qualified = NULL;
> 
> -  if (!gdb_PyArg_ParseTupleAndKeywords (args, kwargs, "|siiOOsssOp", 
> keywords,
> +  if (!gdb_PyArg_ParseTupleAndKeywords (args, kwargs, "|siiOOsssOO", 
> keywords,
>  					&spec, &type, &access_type,
>  					&internal,
>  					&temporary, &source,
> @@ -762,7 +762,7 @@ bppy_init (PyObject *self, PyObject *args, PyObject 
> *kwargs)
>  	  {
>  	    event_location_up location;
>  	    symbol_name_match_type func_name_match_type
> -	      = (qualified
> +	      = (qualified != NULL && PyObject_IsTrue (qualified)
>  		  ? symbol_name_match_type::FULL
>  		  : symbol_name_match_type::WILD);

Pedro gave me a thumbs up on IRC, so I am pushing it.

Simon


      reply	other threads:[~2017-12-14 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 19:53 Simon Marchi
2017-12-14 20:48 ` Simon Marchi [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=ab9e6a453f30cfc886e01576354bdac5@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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