[Webkit-unassigned] [Bug 36816] New: Uninitalised members in BytecodeGenerator and CallLinkInfo

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=36816

           Summary: Uninitalised members in BytecodeGenerator and
                    CallLinkInfo
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: kb at inf.u-szeged.hu


Valgrind shows me 2 uninitalised value problem:

Conditional jump or move depends on uninitialised value(s)
  at 0x51BBB60: cti_vm_lazyLinkCall (JITStubs.cpp:1679)
  by 0x51B0102: JSC::TrampolineStructure::TrampolineStructure() (JITStubs.h:76)
  by 0x5173A5C: JSC::JITCode::execute(JSC::RegisterFile*, JSC::ExecState*,
JSC::JSGlobalData*, JSC::JSValue*) (JITCode.h:77)
  ...

Conditional jump or move depends on uninitialized value(s)
   at 0x513E0DF: JSC::BytecodeGenerator::createArgumentsIfNecessary()
(BytecodeGenerator.cpp:1391)
   by 0x5147EE7: JSC::BytecodeGenerator::emitPushNewScope(JSC::RegisterID*,
JSC::Identifier const&, JSC::RegisterID*)
BytecodeGenerator.cpp:1882)
   by 0x5154205: JSC::TryNode::emitBytecode(JSC::BytecodeGenerator&,
JSC::RegisterID*) (NodesCodegen.cpp:1890)
   ...

These are caused by incomplete member initializer lists. I think the second
could be dangerous.
Fortunately we can solve it by an easy fix.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.