Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [commit] linespec.c, decode_line_1, check for null.
Date: Tue, 01 Mar 2011 22:03:00 -0000	[thread overview]
Message-ID: <4D6D6D2A.6070008@vmware.com> (raw)
In-Reply-To: <201103012150.16696.pedro@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 595 bytes --]

Pedro Alves wrote:
> On Tuesday 01 March 2011 21:43:27, Michael Snyder wrote:
>> Pedro Alves wrote:
>>> On Tuesday 01 March 2011 20:57:30, Michael Snyder wrote:
>>>> If it's worth checking for null, it's worth doing so before the first 
>>>> dereference.
>>> Well, then it may not be worth checking for null.  How old is
>>> that code?  
>> It predates me, and I've been on gdb since 1995.   ;-)
> 
> :-)
> 
> Then I think it's safe to say that if we haven't seen
> a NULL-dereference crash in over 15 years, it's because it's
> not really necessary.
> 

Ok then -- you'd prefer it like this?



[-- Attachment #2: reversenull8.txt --]
[-- Type: text/plain, Size: 1232 bytes --]

2011-03-01  Michael Snyder  <msnyder@vmware.com>

	* linespec.c (decode_line_1): Remove unnecessary null check.

Index: linespec.c
===================================================================
RCS file: /cvs/src/src/gdb/linespec.c,v
retrieving revision 1.111
diff -u -p -u -p -r1.111 linespec.c
--- linespec.c	1 Mar 2011 20:57:52 -0000	1.111
+++ linespec.c	1 Mar 2011 22:01:07 -0000
@@ -726,7 +726,7 @@ decode_line_1 (char **argptr, int funfir
   char *copy;
   /* This says whether or not something in *ARGPTR is quoted with
      completer_quotes (i.e. with single quotes).  */
-  int is_quoted = 0;
+  int is_quoted;
   /* Is *ARGPTR is enclosed in double quotes?  */
   int is_quote_enclosed;
   int is_objc_method = 0;
@@ -745,14 +745,11 @@ decode_line_1 (char **argptr, int funfir
   
   /* See if arg is *PC.  */
 
-  if (*argptr)
-    {
-      if (**argptr == '*')
-	return decode_indirect (argptr);
+  if (**argptr == '*')
+    return decode_indirect (argptr);
 
-      is_quoted = (strchr (get_gdb_completer_quote_characters (),
-			   **argptr) != NULL);
-    }
+  is_quoted = (strchr (get_gdb_completer_quote_characters (),
+		       **argptr) != NULL);
 
   if (is_quoted)
     end_quote = skip_quoted (*argptr);

  reply	other threads:[~2011-03-01 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 20:57 Michael Snyder
2011-03-01 21:25 ` Pedro Alves
2011-03-01 21:43   ` Michael Snyder
2011-03-01 21:50     ` Pedro Alves
2011-03-01 22:03       ` Michael Snyder [this message]
2011-03-01 22:08         ` Pedro Alves

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=4D6D6D2A.6070008@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@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