[lldb-dev] Allocation memory is failing in PPC64le

[Alexandre Yukio Yamashita via lldb-dev]

Hi,

I am trying to implement the expression evaluation for PPC64le using JIT.
But the LLDB is failling to allocate memory when it tries to evaluate an expression.
A Thread Plan is being interrupted before LLDB tries to allocate memory.
How could I check why this plan is not finishing?
What functions should I implement to enable JIT?
I am sending the logs of the issue below.

Thanks.
Alexandre.

lldb             0x10013069c10: tid = 0x976: stop info = breakpoint 1.1 (stop_id = 4)
lldb             Process::RunThreadPlan(): execution interrupted: 0x3fff70006ac0 Event: broadcaster = 0x100130167b8 (lldb.process), type = 0x00000001 (state-changed), data = { process = 0x10013016780 (pid = 2422), state = stopped} <1 threads> <0x0976 [ip 0x1000058c] breakpoint 1.1>
lldb             Process::RunThreadPlan: ExecutionInterrupted - discarding thread plans up to 0x10013076210.
lldb             Discarding thread plans for thread tid = 0x0976, up to 0x10013076210
lldb             0x10013025c10 Broadcaster("lldb.process")::RestoreBroadcaster (about to pop listener("lldb.process.listener.run-thread-plan")=0x10012f85810)
lldb             0x10012f85810 Listener::Clear('lldb.process.listener.run-thread-plan')
lldb             0x10012f85810 Listener::~Listener('lldb.process.listener.run-thread-plan')
lldb             ThreadPlanCallFunction(0x10013076210): DoTakedown called as no-op for thread 0x0976, m_valid: 1 complete: 1.

lldb             Target::RemoveBreakpointByID (break_id = -3, internal = yes)

lldb             Target::DisableBreakpointByID (break_id = -3, internal = yes)

lldb             GDBRemoteCommunicationClient::SendGDBStoppointTypePacket() remove at addr = 0x100003d0
lldb             0x10013017168 Communication::Write (src = 0x10012e7d318, src_len = 17) connection = 0x1001302e610
lldb             0x1001302e610 ConnectionFileDescriptor::Write (src = 0x10012e7d318, src_len = 17)
lldb             0x1001302e610 ConnectionFileDescriptor::Write(fd = 7, src = 0x10012e7d318, src_len = 17) => 17 (error = (null))
lldb             this = 0x0000010013017168, dst = 0x00003FFFED125FC8, dst_len = 8192, timeout = 99999999000000 us, connection = 0x000001001302E610
lldb             this = 0x000001001302E610, timeout = 99999999000000 us
lldb             0x1001302e610 ConnectionFileDescriptor::Read()  fd = 7, dst = 0x3fffed125fc8, dst_len = 8192) => 6, error = (null)
lldb             ProcessGDBRemote::DoAllocateMemory no direct stub support for memory allocation, and InferiorCallMmap also failed - is stub missing register context save/restore capability?
lldb             Process::DoAllocateMemory (byte_size = 0x00001000, permissions = rwx) => 0xffffffffffffffff
lldb             AllocatedMemoryCache::AllocateMemory (byte_size = 0x00000008, permissions = rwx) => 0xffffffffffffffff
lldb             Process::CanJIT pid 2422 allocation test failed, CanJIT () is false: unable to allocate 4096 bytes of memory with permissions rwx
lldb             AllocatedMemoryCache::DeallocateMemory (addr = 0xffffffffffffffff) => 0



--
Alexandre Yukio Yamashita (DSB)
Instituto de Pesquisas Eldorado
www.eldorado.org.br<http://www.eldorado.org.br/>
+55 19 3757 3201 / +55 19 9 8336 5553
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20171205/acf066fa/attachment-0001.html>