Hi Catalin,
disassembly at 0x4f69d0 does not look right though opcode is same. 4f69d0: d2800013 movz x19, #0x0 4f69d4: b9402260 ldr w0, [x19,#32]
It is movz and not just mov. So I think data contents of x19 are okay. I can reproduce this bug consistently. Thanks, Aparna
44cdc4: a9bc7bfd stp x29, x30, [sp,#-64]!
44cdc8: 910003fd mov x29, sp
44cdcc: a90153f3 stp x19, x20, [sp,#16]
44cdd0: aa0003f3 mov x19, x0
44cdd4: aa0203e0 mov x0, x2
44cdd8: a9025bf5 stp x21, x22, [sp,#32]
44cddc: aa0203f4 mov x20, x2
44cde0: aa0103f6 mov x22, x1
44cde4: 2a0303f5 mov w21, w3
44cde8: 9402a6e8 bl 4f6988 JSC::InternalFunction::name(JSC::ExecState*) 44cdec: f9400001 ldr x1, [x0] 44cdf0: b9400022 ldr w2, [x1]
44cdf4: 36100522 tbz w2, #2, 44ce98 <JSC::JSObject::putDirectFunctionWithoutTransition(JSC::ExecState*, JSC::InternalFunction*, unsigned int)+0xd4> 44cdf8: f9001ba1 str x1, [x29,#48]
44cdfc: b9400020 ldr w0, [x1]
44ce00: 11008000 add w0, w0, #0x20
On Thu, May 9, 2013 at 4:01 PM, Catalin Marinas catalin.marinas@arm.comwrote:
On Thu, May 09, 2013 at 10:23:23AM +0100, Aparna Mandke wrote:
Printing disassembly of more instructions in this region:
Can you also get a disassemble around LR (0x44cdec)?
-- Catalin