linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Hannes Eder <hannes@hanneseder.net>
Cc: Christopher Li <sparse@chrisli.org>,
	linux-sparse@vger.kernel.org,
	Nicholas Mc Guire <der.herr@hofr.at>
Subject: Re: [bug, bisected, -chrisl] Segfault at evaluate.c:341
Date: Thu, 19 Mar 2009 19:14:31 +0000	[thread overview]
Message-ID: <20090319191431.GD28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <154e089b0903191138x15b66808v70bc862d7a13e3c2@mail.gmail.com>

On Thu, Mar 19, 2009 at 07:38:51PM +0100, Hannes Eder wrote:

> http://hanneseder.net/sparse/kernel-cred-c.prep.tar.gz
> 
> $ sparse kernel-cred-c.prep.gcc
> 
> produces some warnings as usual.
> 
> $ sparse kernel-cred-c.prep.sparse
> 
> produces some warnings, a boatload of errors, and then segfaults.

Oh, joy.

a) some <expletives> has #define if(x) ....... (check it out, I'm not kidding)
b) ifdef that turd's conditional upon is present in your .config
c) ... and now,
	if (
#ifdef .....
		barf &&
#endif
		vomit)

steps into undefined behaviour.

  reply	other threads:[~2009-03-19 19:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 13:49 [bug, bisected, -chrisl] Segfault at evaluate.c:341 Hannes Eder
2009-03-19 14:46 ` Al Viro
2009-03-19 18:32   ` Nicholas Mc Guire
2009-03-19 18:38   ` Hannes Eder
2009-03-19 19:14     ` Al Viro [this message]
2009-03-19 20:04       ` Christopher Li
2009-03-19 21:52         ` Al Viro
2009-03-19 22:09           ` Al Viro
2009-03-19 23:11             ` Christopher Li
2009-03-21  4:40               ` Al Viro
2009-03-21 17:28                 ` Al Viro
2009-03-23  9:22                   ` Christopher Li

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=20090319191431.GD28946@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=der.herr@hofr.at \
    --cc=hannes@hanneseder.net \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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).