public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [python][patch] Python rbreak
Date: Thu, 16 Nov 2017 14:19:00 -0000	[thread overview]
Message-ID: <87fc8f02-e7d5-0774-627f-b188ab668f74@redhat.com> (raw)
In-Reply-To: <0cac20bb-f383-f83a-e621-99f425f225d6@ericsson.com>

On 14/11/17 20:22, Simon Marchi wrote:
> On 2017-11-03 05:46 AM, Phil Muldoon wrote:
>>>>> I can't find a reference, but I think we want test names to start
>>>>> with a lower case letter and not end with a dot.  I'll see if we
>>>>> can add this to the testcase cookbook wiki page.
>>>>
>>>> As I mentioned on IRC, I've not heard of it but will happily change
>>>> the names to comply.
>>
>> Sorry this took a bit longer to get back out than I would have liked.
>> Modified patch follows. I believe I have incorporated yours, Eli's and
>> Kevin's comments.  ChangeLogs remain the same (other than the new NEWS
>> entry which I have added locally.)
> 
> Hi Phil,
> 
> Sorry for the wait, I had missed the update.  The patch looks good to me,
> with just a nit below.
> 
>> +	  if (obj_name == NULL)
>> +	    return NULL;
>> +
>> +	  /* Is the object file still valid?  */
>> +	  if (obj_name == Py_None)
>> +	    continue;
>> +
>> +	  gdb::unique_xmalloc_ptr<char> filename =
>> +	    python_string_to_target_string (obj_name.get ());
>> +
>> +	  if (filename == NULL)
>> +	    return NULL;
>> +
>> +	  /* Make sure there is a definite place to store the value of
>> +	     s before it is released.  */
> 
> "of s" -> "of filename" ?
> 
> Simon

So committed, with that additional change.

commit d8ae99a7b08e29e31446aee1e47e59943d7d9926

Thanks for the review

Cheers

Phil

      reply	other threads:[~2017-11-16 14:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 11:30 Phil Muldoon
2017-10-11 12:11 ` Eli Zaretskii
2017-10-11 12:27   ` Phil Muldoon
2017-10-11 16:19 ` Kevin Buettner
2017-10-11 16:24   ` Phil Muldoon
2017-10-13  8:08 ` Phil Muldoon
2017-10-16 22:22 ` Simon Marchi
2017-10-16 23:01   ` Phil Muldoon
2017-10-17  0:24     ` Simon Marchi
2017-11-03  9:46       ` Phil Muldoon
2017-11-03 10:05         ` Eli Zaretskii
2017-11-13 19:29         ` Phil Muldoon
2018-02-01  9:47           ` [RFA/RFC] Clarify contents of NEWS entry re: Python "rbreak" (waa: "Re: [python][patch] Python rbreak") Joel Brobecker
2018-02-01 10:26             ` Phil Muldoon
2018-02-01 16:21             ` Eli Zaretskii
2018-02-01 17:32               ` Joel Brobecker
2018-02-01 18:25                 ` Eli Zaretskii
2018-02-02  3:16                   ` Joel Brobecker
2018-02-09  4:30                     ` Joel Brobecker
2018-02-09  9:26                       ` Eli Zaretskii
2018-02-09 12:13                         ` Joel Brobecker
2017-11-14 20:23         ` [python][patch] Python rbreak Simon Marchi
2017-11-16 14:19           ` Phil Muldoon [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=87fc8f02-e7d5-0774-627f-b188ab668f74@redhat.com \
    --to=pmuldoon@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).