From: msnyder@sonic.net
To: msnyder@sonic.net, gdb-patches@sourceware.org
Subject: Re: [OB] cli/cli-script.c, null ptr guard
Date: Thu, 28 Jun 2007 22:27:00 -0000 [thread overview]
Message-ID: <6989.12.7.175.2.1183069038.squirrel@webmail.sonic.net> (raw)
In-Reply-To: <20070628215829.GA10350@caradoc.them.org>
> No, I don't think this is obvious. What does it mean to have a null
> string here and how can it happen? I'm pretty sure it can't, and the
> if check is just clutter.
The reasoning is that, since we checked it for NULL in the
first statement of the function, we must believe that the
possibility exists for it to be NULL.
next prev parent reply other threads:[~2007-06-28 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 21:51 msnyder
2007-06-28 22:15 ` Daniel Jacobowitz
2007-06-28 22:27 ` msnyder [this message]
2007-06-28 22:48 ` Daniel Jacobowitz
2007-06-28 23:06 ` msnyder
2007-07-01 15:56 ` Daniel Jacobowitz
2007-07-03 1:13 ` msnyder
2007-07-03 1:14 ` msnyder
2007-07-03 1:23 ` Daniel Jacobowitz
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=6989.12.7.175.2.1183069038.squirrel@webmail.sonic.net \
--to=msnyder@sonic.net \
--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