Nux

Conditional jump or move depends on uninitialised value(s) at GraphicsDisplayX11.cpp:1677

Bug #919326 reported by Marco Biscaro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nux
Incomplete
Undecided
Unassigned
Unity
Incomplete
Undecided
Unassigned
nux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Relevant valgrind log:

==30807== Conditional jump or move depends on uninitialised value(s)
==30807== at 0x16DAF827: nux::GraphicsDisplay::ProcessXEvent(_XEvent, bool) (GraphicsDisplayX11.cpp:1677)
==30807== by 0x16DAFC2B: nux::GraphicsDisplay::ProcessForeignX11Event(_XEvent*, nux::Event*) (GraphicsDisplayX11.cpp:1352)
==30807== by 0x186C9DBB: nux::WindowThread::ProcessForeignEvent(_XEvent*, void*) (WindowThread.cpp:1270)
==30807== by 0x1811818F: unity::UnityScreen::handleEvent(_XEvent*) (unityshell.cpp:1179)
==30807== by 0x457BE7: CompScreen::handleEvent(_XEvent*) (in /usr/bin/compiz)
==30807== by 0x431969: PrivateScreen::processEvents() (in /usr/bin/compiz)
==30807== by 0x45EAC0: CompEventSource::callback() (in /usr/bin/compiz)
==30807== by 0x623A9DE: Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) (in /usr/lib/libglibmm-2.4.so.1.3.0)
==30807== by 0x66A6A5C: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.0)
==30807== by 0x66A7257: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.0)
==30807== by 0x66A7791: g_main_loop_run (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.0)
==30807== by 0x42E855: CompScreen::eventLoop() (in /usr/bin/compiz)

Running nux revision 538.

Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

These mostly seem X-related (and possibly driver-related as well). Which GPU are you using?

Revision history for this message
Marco Biscaro (marcobiscaro2112) wrote :

From lspci -vv

00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller])
        Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device 2013
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 43
        Region 0: Memory at fe000000 (64-bit, non-prefetchable) [size=4M]
        Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at f080 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0500c Data: 4171
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a4] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel driver in use: i915
        Kernel modules: i915

Revision history for this message
Sven Baars (sbte) wrote :

This is probably because m_WMDeleteWindow is used uninitialized. I'm not sure what it should be set to by default though.

Revision history for this message
Omer Akram (om26er) wrote :

Marco, Thanks for the report. Is that still an issue in Ubuntu 12.04 ?

Changed in unity:
status: New → Incomplete
Changed in nux:
status: New → Incomplete
Changed in nux (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I think the details in this bug are out of date. The line of code moved, but was fixed as bug 983321.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.