Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "Metzger, Markus T" <markus.t.metzger@intel.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add method/format information to =record-started
Date: Tue, 07 Jun 2016 12:53:00 -0000	[thread overview]
Message-ID: <5756C3CD.4070202@ericsson.com> (raw)
In-Reply-To: <86inxlwdhv.fsf@gmail.com>

On 16-06-07 05:32 AM, Yao Qi wrote:
> Simon Marchi <simon.marchi@ericsson.com> writes:
> 
>> Just to be clear, the inner if/else doesn't need them, but the outer one does.
>>
> 
> No, it is not "GDB C Coding Standard" compliant, IMO.  In the quoted url
> I gave,
> 
> "Any two or more lines in code should be wrapped in braces, even if they
> are comments, as they look like separate statements:"

Ahh ok, I thought braces were only needed in the case where you added a comment.

> so...
> 
>> Here's the result:
>>
>>
>>   if (started)
>>     {
>>       if (format != NULL)
> 
> brace is needed here...
> 
>> 	fprintf_unfiltered (
>> 	  mi->event_channel,
>> 	  "record-started,thread-group=\"i%d\",method=\"%s\",format=\"%s\"",
>> 	  inferior->num, method, format);
> 
> and here
> 
>>       else
>> 	fprintf_unfiltered (
>> 	  mi->event_channel,
>> 	  "record-started,thread-group=\"i%d\",method=\"%s\"",
>> 	  inferior->num, method);
>>     }
>>   else
>>     fprintf_unfiltered (mi->event_channel,
>> 			"record-stopped,thread-group=\"i%d\"", inferior->num);

I suppose here too?







  reply	other threads:[~2016-06-07 12:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 15:52 Simon Marchi
2016-06-03 17:03 ` Simon Marchi
2016-06-06  6:38 ` Metzger, Markus T
2016-06-06 13:03   ` Yao Qi
2016-06-06 13:24     ` Simon Marchi
2016-06-07  9:32       ` Yao Qi
2016-06-07 12:53         ` Simon Marchi [this message]
2016-06-07 15:38           ` Yao Qi
2016-06-07 15:48             ` Simon Marchi
2016-06-06 13:07   ` Simon Marchi
2016-06-06 13:20     ` Metzger, Markus T
2016-06-06 13:39       ` Simon Marchi
2016-06-06 13:44         ` Metzger, Markus T
2016-06-06 13:49           ` Simon Marchi
2016-06-06 14:02             ` Metzger, Markus T
2016-06-06 14:28               ` Simon Marchi
2016-06-06 14:33                 ` Metzger, Markus T
2016-06-06 15:13             ` Eli Zaretskii
2016-06-06 21:12               ` Simon Marchi
2016-07-05 13:51 ` Yao Qi
2016-07-05 13:52   ` Simon Marchi

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=5756C3CD.4070202@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=qiyaoltc@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