Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1260872

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

Show all headers | View raw

On 11/02/15 08:58, Thiago Macieira wrote:
> On Monday 02 November 2015 08:44:01 Randy Dunlap wrote:
>>> 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?
>>
>> ASSERT: "!isEmpty()" in file /usr/include/QtCore/qlist.h, line 282
>> ../scripts/kconfig/Makefile:22: recipe for target 'xconfig' failed
>> make[2]: *** [xconfig] Aborted (core dumped)
> [cut]
>> #4  0x00007f858c3eec44 in qFatal(char const*, ...) ()
>>     at /usr/lib64/libQtCore.so.4
>> #5  0x00007f858c3eec8a in  () at /usr/lib64/libQtCore.so.4
>> #6  0x00000000004206cc in ConfigList::updateSelection() ()
> 
> Thanks, Randy.
> 
> This seems to be it:
> 
>         if (selectedItems().count() == 0)
>                 return;
> 
>         ConfigItem* item = (ConfigItem*)selectedItems().first();
> 
> Which means this shouldn't be happening. I don't know how the list could be 
> non-empty in one call and empty in the next.  It's wasteful to call 
> selectedItems() twice (it's not a cheap function), but it shouldn't cause this 
> issue.
> 
> We can easily just cache the result and this is what the attached patch does, 
> but given that this error makes no sense to me, I cannot guarantee that you 
> don't have another problem elsewhere.
> 
> Boris, do you have another idea?
> 

Hi,
What does this patch apply to?
I can't apply it cleanly to to 4.3 or linux-next of yesterday or today.

thanks,

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

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

linux-next: Tree for Nov 1 Stephen Rothwell <sfr@canb.auug.org.au> - 2015-11-01 18:00 +0100
  Re: linux-next: Tree for Nov 1 (lightnvm) Randy Dunlap <rdunlap@infradead.org> - 2015-11-02 02:20 +0100
    Re: linux-next: Tree for Nov 1 (lightnvm) Matias Bjorling <m@bjorling.me> - 2015-11-02 13:50 +0100
      Re: linux-next: Tree for Nov 1 (lightnvm) Jens Axboe <axboe@fb.com> - 2015-11-02 16:40 +0100
        Re: linux-next: Tree for Nov 1 (lightnvm) Matias Bjorling <m@bjorling.me> - 2015-11-02 23:40 +0100
          Re: linux-next: Tree for Nov 1 (lightnvm) Jens Axboe <axboe@fb.com> - 2015-11-03 18:00 +0100
  Re: linux-next: Tree for Nov 1 (xconfig problem) Randy Dunlap <rdunlap@infradead.org> - 2015-11-02 04:20 +0100
    Re: linux-next: Tree for Nov 1 (xconfig problem) Michal Marek <mmarek@suse.cz> - 2015-11-02 14:40 +0100
      Re: linux-next: Tree for Nov 1 (xconfig problem) Thiago Macieira <thiago.macieira@intel.com> - 2015-11-02 15:00 +0100
        Re: linux-next: Tree for Nov 1 (xconfig problem) Randy Dunlap <rdunlap@infradead.org> - 2015-11-02 17:50 +0100
          Re: linux-next: Tree for Nov 1 (xconfig problem) Thiago Macieira <thiago.macieira@intel.com> - 2015-11-02 18:00 +0100
            Re: linux-next: Tree for Nov 1 (xconfig problem) Randy Dunlap <rdunlap@infradead.org> - 2015-11-02 19:50 +0100
              Re: linux-next: Tree for Nov 1 (xconfig problem) Thiago Macieira <thiago.macieira@intel.com> - 2015-11-02 20:30 +0100
                Re: linux-next: Tree for Nov 1 (xconfig problem) Michal Marek <mmarek@suse.cz> - 2015-11-02 21:50 +0100
      Re: linux-next: Tree for Nov 1 (xconfig problem) Randy Dunlap <rdunlap@infradead.org> - 2015-11-02 17:10 +0100
  Re: linux-next: Tree for Nov 1 Geert Uytterhoeven <geert@linux-m68k.org> - 2015-11-02 09:10 +0100

csiph-web