Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix mi-break.exp: 'b "basics.c":16'
Date: Thu, 09 May 2002 15:31:00 -0000	[thread overview]
Message-ID: <20020509223119.GC14492@nevyn.them.org> (raw)
In-Reply-To: <20020402192959.A17349@nevyn.them.org>

On Tue, Apr 02, 2002 at 07:29:59PM -0500, Daniel Jacobowitz wrote:
> [I dislike decode_line_1.  But that seems to be the general consensus...]
> 
> There was a logic error in the code to handle "file":line.  Several,
> actually.  I suspect that it once worked and had bitrotten as the behavior
> of the function changed.  For instance, at the beginning of the function:
> 
>   if (p[0] == '"')
>     {
>       is_quote_enclosed = 1;
>       (*argptr)++;
>       p++;
>     }
> 
> Then below it checked 'is_quote_enclosed && (**argptr) == '"').  That'll
> only be true given a literal '"":<line>', which was not the intent of the
> test.
> 
> 
> This patch updates the behavior, should change nothing else, and causes no
> regressions.  OK to check in?

Only Michael Chastain (who recommended it for approval) had anything to
say about this patch.  Ping?


> 2002-04-02  Daniel Jacobowitz  <drow@mvista.com>
> 
> 	* linespec.c (decode_line_1): Check for a double quote after
> 	a filename correctly.
> 
> Index: linespec.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/linespec.c,v
> retrieving revision 1.17
> diff -u -p -r1.17 linespec.c
> --- linespec.c	2002/03/22 18:57:07	1.17
> +++ linespec.c	2002/04/03 00:19:30
> @@ -929,20 +929,12 @@ decode_line_1 (char **argptr, int funfir
>        if ((*p == '"') && is_quote_enclosed)
>  	--p;
>        copy = (char *) alloca (p - *argptr + 1);
> -      if ((**argptr == '"') && is_quote_enclosed)
> -	{
> -	  memcpy (copy, *argptr + 1, p - *argptr - 1);
> -	  /* It may have the ending quote right after the file name */
> -	  if (copy[p - *argptr - 2] == '"')
> -	    copy[p - *argptr - 2] = 0;
> -	  else
> -	    copy[p - *argptr - 1] = 0;
> -	}
> +      memcpy (copy, *argptr, p - *argptr);
> +      /* It may have the ending quote right after the file name */
> +      if (is_quote_enclosed && copy[p - *argptr - 1] == '"')
> +	copy[p - *argptr - 1] = 0;
>        else
> -	{
> -	  memcpy (copy, *argptr, p - *argptr);
> -	  copy[p - *argptr] = 0;
> -	}
> +	copy[p - *argptr] = 0;
>  
>        /* Find that file's data.  */
>        s = lookup_symtab (copy);
> 

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-05-09 22:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 16:29 Daniel Jacobowitz
2002-05-09 15:31 ` Daniel Jacobowitz [this message]
2002-05-09 15:35   ` Elena Zannoni
2002-05-09 15:53 ` Michael Snyder
2002-05-09 16:05   ` Daniel Jacobowitz
2002-05-09 16:32     ` Elena Zannoni
2002-05-10 12:50       ` Daniel Jacobowitz
2002-04-03  7:58 Michael Elizabeth Chastain
2002-04-03  8:20 ` Daniel Jacobowitz
2002-04-03  8:39 Michael Elizabeth Chastain
2002-04-03  9:39 Michael Elizabeth Chastain

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=20020509223119.GC14492@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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