Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: ali_anwar <ali_anwar@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix for PR15117
Date: Fri, 02 Aug 2013 17:49:00 -0000	[thread overview]
Message-ID: <51FBF127.7000108@redhat.com> (raw)
In-Reply-To: <51FBA2A6.8000307@codesourcery.com>

This looks great! Thank you for the expanded comments. That cleared a 
misconception I had. I was incorrect asserting that your convenience 
variable change was not located properly.

On 08/02/2013 05:14 AM, ali_anwar wrote:
> There are already test cases in the gdb.base/break.exp for this scenario
> (break $foo) and they did get pass. The undefined scenario is already
> covered in gdb.linespec/ls-errs.exp and all test cases in gdb.linespec/*
> got passed.
[snip]

Great! Thank you for pointing that out.

Two tiny nits:

> Index: linespec.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/linespec.c,v
> retrieving revision 1.185
> diff -u -r1.185 linespec.c
> --- linespec.c	30 May 2013 16:57:38 -0000	1.185
> +++ linespec.c	2 Aug 2013 11:43:57 -0000
> @@ -1649,7 +1649,7 @@
>     else
>       {
>         /* NAME was not a function or a method.  So it must be a label
> -	 name.  */
> +	 name or user specified variable like "break foo.c:$zippo".  */
>         labels = find_label_symbols (PARSER_STATE (parser), NULL,
>   				   &symbols, name);
>         if (labels != NULL)
> @@ -1660,6 +1660,22 @@
>   	  symbols = NULL;
>   	  discard_cleanups (cleanup);
>   	}
> +      else if (token.type == LSTOKEN_STRING
> +	       && *LS_TOKEN_STOKEN (token).ptr == '$')
> +	{
> +	  /* User specified a convenience variable or history value.  */
> +	  PARSER_RESULT (parser)->line_offset
> +	    = linespec_parse_variable (PARSER_STATE (parser), name);
> +
> +	  if (PARSER_RESULT (parser)->line_offset.sign == LINE_OFFSET_UNKNOWN)
> +	    {
> +	      /* Not able to parse user specified variable. Do not
> +		 throw an error here. parse_linespec will do it for us*/

This comment is not formatted properly: two spaces after '.'. Use 
complete sentences (where possible/feasible). This should probably read:

/* The user-specified variable was not valid.  Do not
    throw an error here.  parse_linespec will do it for us.  */

[i.e, just copy the bits from the following block]

> +	      PARSER_RESULT (parser)->function_name = name;
> +	      discard_cleanups (cleanup);
> +	      return;
> +	    }
> +	}
>         else
>   	{
>   	  /* The name is also not a label.  Abort parsing.  Do not throw
> Index: testsuite/gdb.base/break.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/break.exp,v
> retrieving revision 1.58
> diff -u -r1.58 break.exp
> --- testsuite/gdb.base/break.exp	7 Jun 2013 17:31:07 -0000	1.58
> +++ testsuite/gdb.base/break.exp	2 Aug 2013 11:54:40 -0000
> @@ -957,6 +957,18 @@
>       }
>   }
>
> +#
> +# Test break via convenience variable with file name
> +#
> +set line [gdb_get_line_number "set breakpoint 1 here"]
> +gdb_test_no_output "set \$l = $line"

I'm showing extra whitespace at the end of the above line.  Could you 
double-check that before committing?

> +gdb_breakpoint ${srcfile}:\$l
> +
> +gdb_test_no_output "set \$foo=81.5" \
> +    "set convenience variable \$foo to 81.5"
> +gdb_test "break $srcfile:\$foo" \
> +    "Convenience variables used in line specs must have integer values.*" \
> +    "set breakpoint via non-integer convenience variable disallowed"
>
>   # Reset the default arguments for VxWorks
>   if [istarget "*-*-vxworks*"] {
>

With those trivial things fixed, I think this patch is ready for a 
global maintainer to review and approve.

Thanks again!
Keith


  reply	other threads:[~2013-08-02 17:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 16:55 ali_anwar
2013-07-30 18:56 ` Keith Seitz
2013-08-02 12:14   ` ali_anwar
2013-08-02 17:49     ` Keith Seitz [this message]
2013-08-06 19:51       ` ali_anwar
2013-08-07  5:42       ` ali_anwar
2013-08-07 20:01         ` Tom Tromey
2013-08-08 14:56           ` Pedro Alves
2013-08-08 20:05             ` Tom Tromey
2013-08-12 12:12           ` ali_anwar

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=51FBF127.7000108@redhat.com \
    --to=keiths@redhat.com \
    --cc=ali_anwar@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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