From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christian Eggers <ceggers@arri.de>
Cc: linux-sparse@vger.kernel.org, Dirk Mueller <dmueller@suse.com>,
Jiri Slaby <jirislaby@gmail.com>
Subject: Re: Segmentation fault when running sparse with current linux master
Date: Thu, 24 Sep 2020 21:38:17 +0200 [thread overview]
Message-ID: <20200924193817.5ilitvaqneach5pg@ltop.local> (raw)
In-Reply-To: <4184357.m9dUj1Odhv@n95hx1g2>
On Mon, Sep 21, 2020 at 09:44:00AM +0200, Christian Eggers wrote:
> Hi Luc,
>
> On Thursday, 17 September 2020, 16:20:17 CEST, Luc Van Oostenryck wrote:
> > On Thu, Sep 17, 2020 at 01:08:57PM +0200, Christian Eggers wrote:
> > > Build of the current linux kernel breaks on my system due to segmentation
> > > fault when running sparse.
> > >
> > > Sparse version: 0.6.2 (built by openSUSE build service)
> >
> > Hi,
> >
> > This has already been reported and fixed in the main tree in late July.
> > It's not clear to me if the latest OpenSUSE packages for sparse contain
> > or not the needed fix.
> >
> > Can you try the version compiled from the source? It's super-easy:
> > cd $dir
> > git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git
> > cd sparse
> > make
> > cp sparse ~/bin/
> >
>
> I fetched the source RPM from openSUSE and replaced the 0.6.2 tar.xz with the
> current master. After building an updating the RPM, sparse doesn't crash
> anymore.
>
> openSUSE ships two versions of sparse [1]:
> - official release: 20180324
> - experimental: 0.6.2
>
> It seems that both version are affected from this problem. The "experimental"
> version should be automatically updated after a new version of sparse is
> released. The "official release" will probably only accept patches resolving
> specific problems. If you can provide a patch against 20180324, I would try to
> write a bug report against the openSUSE package. This could save some time for
> the next person stumbling over this problem... If you provide the commit id,
> openSUSE can also decide themself whether to fix or upgrade the current
> version.
In the official tree, there is a branch 'maint-v0.6.2' which just contain
4 patches fixing some problems with the release v0.6.2, the second patch
77f35b796cc8 ("generic: fix missing inlining of generic expression")
being the one fixing this problem.
For info, I'll most probably make a new full release in a few weeks
(rc1 in 7-10 days, release 1-2 weeks later).
Best regards
-- Luc
next prev parent reply other threads:[~2020-09-24 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 11:08 Segmentation fault when running sparse with current linux master Christian Eggers
2020-09-17 14:20 ` Luc Van Oostenryck
2020-09-21 7:44 ` Christian Eggers
2020-09-24 19:38 ` Luc Van Oostenryck [this message]
2020-09-25 5:37 ` Jiri Slaby
2020-09-25 8:46 ` Luc Van Oostenryck
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=20200924193817.5ilitvaqneach5pg@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=ceggers@arri.de \
--cc=dmueller@suse.com \
--cc=jirislaby@gmail.com \
--cc=linux-sparse@vger.kernel.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).