linux-kernel - Re: linux-next: Tree for Nov 1 (xconfig problem)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2030804.WKiRYyHexJ@tjmaciei-mobl4>
Date:	Mon, 02 Nov 2015 08:51:40 -0500
From:	Thiago Macieira <thiago.macieira@...el.com>
To:	Michal Marek <mmarek@...e.cz>
Cc:	Randy Dunlap <rdunlap@...radead.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-kbuild <linux-kbuild@...r.kernel.org>,
	Boris Barbulovski <bbarbulovski@...il.com>
Subject: Re: linux-next: Tree for Nov 1 (xconfig problem)

On Monday 02 November 2015 14:39:16 Michal Marek wrote:
> On 2015-11-02 04:11, Randy Dunlap wrote:
> > On 11/01/15 08:53, Stephen Rothwell wrote:
> >> Hi all,
> >> 
> >> I start again a day early, and this is how you all repay me? ;-)
> > 
> >> Changes since 20151022:
> > on x86_64:
> > 
> > 'make xconfig' dies a quick death when I try to use it:
> > 
> > linux-next-20151101> ASSERT: "!isEmpty()" in file
> > /usr/include/QtCore/qlist.h, line 282
> Added Boris and Thiago to Cc.
> 
> Are you using Qt4 or Qt5? An

Given the line number, it's a Qt 4.

Randy, we need a backtrace. The problem is on the function that called 
first(). Can you make sure the crash generates a core dump, then get the bt 
from that?

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/