Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Tom Tromey <tromey@redhat.com>,    <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3 02/15] Save trace into CTF format
Date: Thu, 14 Mar 2013 17:49:00 -0000	[thread overview]
Message-ID: <20802.3504.290457.930526@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <514055B3.6040306@codesourcery.com>

Hi.  Just some nits.

Yao Qi writes:
 > 2013-03-13  Hui Zhu  <hui_zhu@mentor.com>
 > 	    Yao Qi  <yao@codesourcery.com>
 > 
 > 	* Makefile.in (REMOTE_OBS): Add ctf.o.
 > 	(SFILES): Add ctf.c.
 > 	(HFILES_NO_SRCDIR): Add ctf.h.
 > 	* ctf.c, ctf.h: New files.
 > 	* tracepoint.c : Include 'ctf.h'.
 > 	(collect_pseudocommand): Remove static.
 > 	(trace_save_command): Parse option "-ctf".
 > 	Produce different trace file writers per option.
 > 	Adjust output message.
 > 	(trace_save_tfile, trace_save_ctf): New.
 > 	* tracepoint.h (trace_save_tfile, trace_save_ctf): Declare.
 > 	* mi/mi-main.c: Include 'ctf.h'.
 > 	(mi_cmd_trace_save): Handle option '-ctf'.  Call either
 > 	trace_save_tfile or trace_save_ctf.

 > +/* Write a unsigned 32-bit integer to datastream file represented by
 > +   HANDLER.  */
 > +
 > +#define ctf_save_write_uint32(HANDLER, U32) \
 > +  ctf_save_write (HANDLER, (gdb_byte *) &U32, 4)

Technically speaking, HANDLE and U32 should be in parens.
Also, I think convention is that they be lowercase
(still uppercase in the comment).
[One might also just want to make this a function instead of a macro,
but either way is fine with me at least for now.]

 > +/* This is the implementation of trace_file_write_ops method
 > +   start.  It creates the directory DIRNAME, metadata and datastream
 > +   in the directory.  */
 > +
 > +static void
 > +ctf_start (struct trace_file_writer *self, const char *dirname)
 > +{
 > +  char *file_name;
 > +  struct cleanup *old_chain;
 > +  struct ctf_trace_file_writer *writer
 > +    = (struct ctf_trace_file_writer *) self;
 > +  int i;
 > +
 > +  /* Create DIRNAME.  */
 > +  if (mkdir (dirname, S_IRWXU | S_IRGRP | S_IXGRP | S_IROTH | S_IXOTH)
 > +      && errno != EEXIST)
 > +    error (_("Unable to open directory '%s' for saving trace data (%s)"),
 > +	   dirname, safe_strerror (errno));

I see remote-fileio.c doesn't assume S_IXGRP,et.al. are portable.
Probably want to do the same here.


  parent reply	other threads:[~2013-03-14 17:49 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09  3:48 [PATCH v3 00/15] CTF Support Yao Qi
2013-03-09  3:49 ` [PATCH v3 14/15] Test on saving tracepoint defs: CTF Yao Qi
2013-03-12 20:23   ` Tom Tromey
2013-03-13  9:55     ` Yao Qi
2013-03-13 15:49       ` Tom Tromey
2013-03-09  3:49 ` [PATCH v3 15/15] MAINTAINERS Yao Qi
2013-03-09  3:49 ` [PATCH v3 05/15] ctf test: report.exp Yao Qi
2013-03-12 19:25   ` Tom Tromey
2013-03-09  3:49 ` [PATCH v3 04/15] ctf doc and NEWS Yao Qi
2013-03-09  3:49 ` [PATCH v3 03/15] Read CTF by the ctf target Yao Qi
2013-03-13 20:09   ` Tom Tromey
2013-03-14 13:23     ` Yao Qi
2013-03-14 14:59       ` Tom Tromey
2013-03-14 16:57     ` Doug Evans
2013-03-14 17:39       ` Doug Evans
2013-03-25 13:33         ` Yao Qi
2013-03-25 17:14           ` Doug Evans
2013-03-26 16:16             ` Yao Qi
2013-03-29 17:56               ` Doug Evans
2013-04-08 14:19                 ` Yao Qi
2013-04-08 21:48                   ` Doug Evans
2013-04-09 15:23                     ` Yao Qi
2013-04-09 18:41                       ` Doug Evans
2013-03-09  3:49 ` [PATCH v3 10/15] tstatus.exp: ctf Yao Qi
2013-03-12 19:48   ` Tom Tromey
2013-03-09  3:49 ` [PATCH v3 12/15] Write tracepoint definition in CTF and read Yao Qi
2013-03-12 20:02   ` Tom Tromey
2013-03-14 18:34   ` Doug Evans
2013-03-09  3:49 ` [PATCH v3 02/15] Save trace into CTF format Yao Qi
2013-03-12 18:49   ` Tom Tromey
2013-03-13 10:33     ` Yao Qi
2013-03-13 19:30       ` Tom Tromey
2013-03-14 17:49       ` Doug Evans [this message]
2013-03-09  3:49 ` [PATCH v3 13/15] Test on saving tracepoint defs Yao Qi
2013-03-12 20:10   ` Tom Tromey
2013-03-13  9:48     ` Yao Qi
2013-03-13 14:58       ` Tom Tromey
2013-03-09  3:49 ` [PATCH v3 06/15] Write status to CTF and read Yao Qi
2013-03-12 19:31   ` Tom Tromey
2013-03-14 18:06   ` Doug Evans
2013-03-29 14:46     ` Yao Qi
2013-03-29 16:47       ` Doug Evans
2013-03-09  3:49 ` [PATCH v3 08/15] Write 'stop_desc' of trace status to tfile Yao Qi
2013-03-12 19:15   ` Tom Tromey
2013-03-09  3:49 ` [PATCH v3 09/15] Check the tstatus output on tfile target Yao Qi
2013-03-12 19:45   ` Tom Tromey
2013-03-09  3:49 ` [PATCH v3 07/15] Write trace notes and username into tfile Yao Qi
2013-03-12 19:35   ` Tom Tromey
2013-03-09  3:49 ` [PATCH v3 01/15] Refactor 'tsave' Yao Qi
2013-03-12 18:30   ` Tom Tromey
2013-03-13 10:33     ` Yao Qi
2013-03-13 19:26       ` Tom Tromey
2013-03-14  9:17         ` Yao Qi
2013-03-09  3:49 ` [PATCH v3 11/15] Write tsv definition in CTF and read Yao Qi
2013-03-12 19:56   ` Tom Tromey
2013-04-10 19:16 ` [PATCH v3 00/15] CTF Support Yao Qi
2013-04-11 22:59   ` [patch] Regenerate config.in [Re: [PATCH v3 00/15] CTF Support] Jan Kratochvil
2013-04-12 22:27     ` [commit] " Jan Kratochvil
2014-08-04 18:59   ` Incorrect placement of babeltrace gdb/NEWS item " Jan Kratochvil
2014-08-06  1:30     ` Yao Qi

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=20802.3504.290457.930526@ruffy2.mtv.corp.google.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    --cc=yao@codesourcery.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