Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH v3 03/15] Read CTF by the ctf target
Date: Wed, 13 Mar 2013 20:09:00 -0000	[thread overview]
Message-ID: <871ubjawq8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1362800844-27940-4-git-send-email-yao@codesourcery.com> (Yao	Qi's message of "Sat, 9 Mar 2013 11:47:12 +0800")

>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:

Yao> +AC_ARG_WITH(babeltrace,
Yao> +	    AC_HELP_STRING([--with-babeltrace],
Yao> +			   [Specify prefix directory for the installed
Yao> +			   BABELTRACE package Equivalent to
Yao> +			   --with-babeltrace-include=PATH/include
Yao> +                           plus --with-babeltrace-lib=PATH/lib]))

I think this is missing a period and a space between "package" and
"Equivalent", but see below.

Yao> +if test "x$with_bt_include" != x; then
Yao> +  LIBBABELTRACE_CFLAGS="-I$with_bt_include "
Yao> +fi
Yao> +if test "x$with_bt_lib" != x; then
Yao> +  LIBBABELTRACE="-L$with_bt_lib -lbabeltrace -lbabeltrace-ctf"
Yao> +fi
Yao> +
Yao> +if test "x$with_babeltrace" != "xno"; then

This only checks for libbabeltrace if --with-babeltrace is specified.
So, the text above about equivalency isn't really correct, at least the
way I read it; if you want to give --with-babeltrace-include, you have
to also give --with-babeltrace.

I'm not sure how to reword the above to make it more clear.
Perhaps spelling out the options.

Yao> +
Yao> +static void
Yao> +ctf_close_dir (void)

Lots of functions missing intro comments.
Most of the comments can be really short, since these are just
implementations of target methods.

Yao> +	      /*
Yao> +	      gdb_assert (mlen == bt_ctf_get_array_len (decl));
Yao> +	      contents = bt_ctf_get_char_array (array);
Yao> +	      */

I think just delete this.

Yao> +static int
Yao> +ctf_has_all_memory (struct target_ops *ops)
Yao> +{
Yao> +  return 0;
Yao> +}

Unfortunately for you there is plenty of this patch I don't feel
competent to review.  I don't know much about the target API.

If nobody else looks after a decent interval, ping me and I will ok it.
I suppose if these methods parallel the existing tfile target, then that
is pretty good evidence for it being ok.

The rest seems ok to me.

Tom


  reply	other threads:[~2013-03-13 20:09 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 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 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 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-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 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 05/15] ctf test: report.exp Yao Qi
2013-03-12 19:25   ` Tom Tromey
2013-03-09  3:49 ` [PATCH v3 15/15] MAINTAINERS 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 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
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 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 [this message]
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-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=871ubjawq8.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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