Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'gdb-patches\@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [patch] Tweak output of -var-info-path-expression
Date: Wed, 10 Aug 2011 14:47:00 -0000	[thread overview]
Message-ID: <m3obzxqq7a.fsf@fleche.redhat.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC5784D50AC1@EUSAACMS0703.eamcs.ericsson.se>	(Marc Khouzam's message of "Fri, 5 Aug 2011 09:54:46 -0400")

>>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:

Marc> I'd like to re-submit a workaround I posted about a year ago,
Marc> but never followed through with.

Marc> So, here is the patch with a test.  The test fails with 
Marc> the current HEAD (gets the syntax error) and succeeds with
Marc> the patch applied.  I've also had to update other tests
Marc> to match the change.

I think it is reasonable, just a few nits in the patch.

Marc> Index: gdb/testsuite/gdb.mi/gdb11912.cc

Jan has asked that new tests be given descriptive names instead of PR
numbers.

Marc> +if $verbose>1 then {
Marc> +    send_user "var-info-path-expression returned $cmd_output\n"
Marc> +    send_user "Using $path for data-evaluate-expression\n"
Marc> +}

Just use the verbose command with the level as an argument, like:

    verbose "var-info-path-expression returned $cmd_output" 2

(Note no \n as well.)

Marc> +		 When we are in the scope of the base class or of one
Marc> +	     of its children, the type field name will be interpreted
Marc> +	     as a constructor, if it exists.  Therefore, we must
Marc> +	     indicate that the name is a class name by using the
Marc> +	     'class' keyword.  */

I'd like this comment to have a reference to the PR, either the URL or
"PR mi/11912".

Tom


  reply	other threads:[~2011-08-10 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 13:55 Marc Khouzam
2011-08-10 14:47 ` Tom Tromey [this message]
2011-08-23 13:04   ` Marc Khouzam
2011-08-25 17:44     ` Tom Tromey
2011-08-26  1:48     ` Joel Brobecker
2011-08-26 12:36       ` Marc Khouzam
2011-08-26 20:59         ` [patch] testsuite: unreliable gdb.mi/mi-inheritance-syntax-error.exp [Re: [patch] Tweak output of -var-info-path-expression] Jan Kratochvil
2011-08-26 21:04           ` Tom Tromey
2011-08-26 21:12             ` Jan Kratochvil
2011-08-29 12:16               ` Marc Khouzam

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=m3obzxqq7a.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc.khouzam@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