From: Christopher Li <sparse@chrisli.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
Sparse <linux-sparse@vger.kernel.org>,
Josh Triplett <josh@freedesktop.org>
Subject: Re: [PATCH] Re: Sparse just seg faulted on me!
Date: Wed, 14 Feb 2007 12:36:55 -0800 [thread overview]
Message-ID: <20070214203655.GD18753@chrisli.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702141242460.20368@woody.linux-foundation.org>
On Wed, Feb 14, 2007 at 12:48:17PM -0800, Linus Torvalds wrote:
> Yeah. I started out leaving bad stuff as NULL originally, but over time,
> as I noticed SIGSEGV's, I mostly changed the ones that I ended up having
> trigger to &bad_ctype.
>
> Otherwise we either need to test for NULL all the time (and especially
> since NULL under _some_ circumstances is ok and means "not evaluated yet",
> that can be confusing), and having to pass up errors higher and higher up.
I think I run into the exact same situations. It start out as simple
rules "&bad_ctype" means error. But then all the test against NULL need
to change to test against &bad_ctpye as well. It is getting subtle for
some place NULL means not evaluated yet.
Chris
next prev parent reply other threads:[~2007-02-14 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 9:04 Sparse just seg faulted on me! Anton Altaparmakov
2007-02-14 17:29 ` [PATCH] " Christopher Li
2007-02-14 18:24 ` Linus Torvalds
2007-02-14 19:54 ` Christopher Li
2007-02-14 20:18 ` Christopher Li
2007-02-23 2:25 ` Josh Triplett
2007-02-14 20:48 ` Linus Torvalds
2007-02-14 20:36 ` Christopher Li [this message]
2007-02-23 2:42 ` Josh Triplett
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=20070214203655.GD18753@chrisli.org \
--to=sparse@chrisli.org \
--cc=aia21@cam.ac.uk \
--cc=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.