linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Eggers <ceggers@arri.de>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: <linux-sparse@vger.kernel.org>
Subject: Re: Segmentation fault when running sparse with current linux master
Date: Mon, 21 Sep 2020 09:44:00 +0200	[thread overview]
Message-ID: <4184357.m9dUj1Odhv@n95hx1g2> (raw)
In-Reply-To: <20200917142017.5fhdjdfrwjyjqlpu@ltop.local>

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.

Best regards
Christian

[1] https://software.opensuse.org/package/sparse




  reply	other threads:[~2020-09-21  8:17 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 [this message]
2020-09-24 19:38     ` Luc Van Oostenryck
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=4184357.m9dUj1Odhv@n95hx1g2 \
    --to=ceggers@arri.de \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.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).