linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Undetected error cases
Date: Sun, 1 Jun 2008 21:46:28 +0200	[thread overview]
Message-ID: <19f34abd0806011246nd615793o7e09ceae8dee73e6@mail.gmail.com> (raw)
In-Reply-To: <1212346705.2727.6.camel@dv>

On Sun, Jun 1, 2008 at 8:58 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Sun, 2008-06-01 at 20:42 +0200, Vegard Nossum wrote:
>
>> None of these produce errors or even warnings when they are run
>> through sparse. I probably won't get around to fixing these myself
>> since I'm not that familiar with sparse internals. This is just a
>> heads up :-)
>
> Still, you may be able to create test cases for the testsuite.

Ah, that's be true. I have now submitted the .c files that should
produce the errors/warnings, but I can't seem to find an actual
testsuite in which to hook them. The existing test-* files seem to
test the API, not the files to be parsed.

Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  reply	other threads:[~2008-06-01 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01 18:42 Undetected error cases Vegard Nossum
2008-06-01 18:55 ` Vegard Nossum
2008-06-01 18:58 ` Pavel Roskin
2008-06-01 19:46   ` Vegard Nossum [this message]
2008-06-01 20:10     ` Pavel Roskin

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=19f34abd0806011246nd615793o7e09ceae8dee73e6@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=proski@gnu.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;
as well as URLs for NNTP newsgroup(s).