edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  Issues reported by Clang static analyzer
Date: Tue, 05 Aug 2014 07:11:03 -0400	[thread overview]
Message-ID: <20140705071103.eklhad@comcast.net> (raw)

I think these should be investigated, and fixed.
I fixed the first one, an uninitialized pointer.
I think it was fine the way it was, really,
would only cause trouble on a situation that I know can never occur,
but the compiler can't know that, and it's good practice to initialize things,
so why not.
If any of you want to review some of these errors, feel free,
otherwise I'll explore them as time permits.
Likely fix them one at a time,
one this week, one next week, etc,
so perhaps several small deltas.

Karl Dahlke

             reply	other threads:[~2014-08-05 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 11:11 Karl Dahlke [this message]
2014-08-05 11:28 ` Chris Brannon
  -- strict thread matches above, loose matches on Subject: below --
2014-07-31  7:54 Paul Onyschuk

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=20140705071103.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.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;
as well as URLs for NNTP newsgroup(s).