2021-03-23 16:22:26 +00:00
|
|
|
"""
|
|
|
|
|
Test python scripted process in lldb
|
|
|
|
|
"""
|
|
|
|
|
|
|
|
|
|
import os
|
|
|
|
|
|
|
|
|
|
import lldb
|
|
|
|
|
from lldbsuite.test.decorators import *
|
|
|
|
|
from lldbsuite.test.lldbtest import *
|
|
|
|
|
from lldbsuite.test import lldbutil
|
|
|
|
|
from lldbsuite.test import lldbtest
|
|
|
|
|
|
|
|
|
|
|
2021-07-20 13:00:54 +00:00
|
|
|
class ScriptedProcesTestCase(TestBase):
|
2021-03-23 16:22:26 +00:00
|
|
|
|
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
|
|
|
|
|
|
def setUp(self):
|
|
|
|
|
TestBase.setUp(self)
|
|
|
|
|
self.source = "main.c"
|
|
|
|
|
|
|
|
|
|
def tearDown(self):
|
|
|
|
|
TestBase.tearDown(self)
|
|
|
|
|
|
|
|
|
|
def test_python_plugin_package(self):
|
|
|
|
|
"""Test that the lldb python module has a `plugins.scripted_process`
|
|
|
|
|
package."""
|
|
|
|
|
self.expect('script import lldb.plugins',
|
|
|
|
|
substrs=["ModuleNotFoundError"], matching=False)
|
|
|
|
|
|
|
|
|
|
self.expect('script dir(lldb.plugins)',
|
|
|
|
|
substrs=["scripted_process"])
|
|
|
|
|
|
|
|
|
|
self.expect('script import lldb.plugins.scripted_process',
|
|
|
|
|
substrs=["ModuleNotFoundError"], matching=False)
|
|
|
|
|
|
|
|
|
|
self.expect('script dir(lldb.plugins.scripted_process)',
|
|
|
|
|
substrs=["ScriptedProcess"])
|
|
|
|
|
|
|
|
|
|
self.expect('script from lldb.plugins.scripted_process import ScriptedProcess',
|
|
|
|
|
substrs=["ImportError"], matching=False)
|
|
|
|
|
|
|
|
|
|
self.expect('script dir(ScriptedProcess)',
|
|
|
|
|
substrs=["launch"])
|
|
|
|
|
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
def test_scripted_process_and_scripted_thread(self):
|
2021-07-20 13:00:54 +00:00
|
|
|
"""Test that we can launch an lldb scripted process using the SBAPI,
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
check its process ID, read string from memory, check scripted thread
|
|
|
|
|
id, name stop reason and register context.
|
|
|
|
|
"""
|
2021-07-20 13:00:54 +00:00
|
|
|
self.build()
|
|
|
|
|
target = self.dbg.CreateTarget(self.getBuildArtifact("a.out"))
|
|
|
|
|
self.assertTrue(target, VALID_TARGET)
|
|
|
|
|
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
scripted_process_example_relpath = 'dummy_scripted_process.py'
|
2021-07-20 13:00:54 +00:00
|
|
|
os.environ['SKIP_SCRIPTED_PROCESS_LAUNCH'] = '1'
|
|
|
|
|
self.runCmd("command script import " + os.path.join(self.getSourceDir(),
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
scripted_process_example_relpath))
|
2021-07-20 13:00:54 +00:00
|
|
|
|
|
|
|
|
launch_info = lldb.SBLaunchInfo(None)
|
|
|
|
|
launch_info.SetProcessPluginName("ScriptedProcess")
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
launch_info.SetScriptedProcessClassName("dummy_scripted_process.DummyScriptedProcess")
|
2021-07-20 13:00:54 +00:00
|
|
|
|
|
|
|
|
error = lldb.SBError()
|
|
|
|
|
process = target.Launch(launch_info, error)
|
|
|
|
|
self.assertTrue(process and process.IsValid(), PROCESS_IS_VALID)
|
|
|
|
|
self.assertEqual(process.GetProcessID(), 42)
|
|
|
|
|
|
2021-10-06 00:09:20 +00:00
|
|
|
self.assertEqual(process.GetNumThreads(), 1)
|
|
|
|
|
|
|
|
|
|
thread = process.GetSelectedThread()
|
|
|
|
|
self.assertTrue(thread, "Invalid thread.")
|
|
|
|
|
self.assertEqual(thread.GetThreadID(), 0x19)
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
self.assertEqual(thread.GetName(), "DummyScriptedThread.thread-1")
|
2021-10-06 00:09:20 +00:00
|
|
|
self.assertEqual(thread.GetStopReason(), lldb.eStopReasonSignal)
|
|
|
|
|
|
|
|
|
|
self.assertGreater(thread.GetNumFrames(), 0)
|
|
|
|
|
|
|
|
|
|
frame = thread.GetFrameAtIndex(0)
|
|
|
|
|
register_set = frame.registers # Returns an SBValueList.
|
|
|
|
|
for regs in register_set:
|
|
|
|
|
if 'GPR' in regs.name:
|
|
|
|
|
registers = regs
|
|
|
|
|
break
|
|
|
|
|
|
|
|
|
|
self.assertTrue(registers, "Invalid General Purpose Registers Set")
|
|
|
|
|
self.assertEqual(registers.GetNumChildren(), 21)
|
|
|
|
|
for idx, reg in enumerate(registers, start=1):
|
|
|
|
|
self.assertEqual(idx, int(reg.value, 16))
|
|
|
|
|
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
def test_launch_scripted_process_stack_frames(self):
|
2021-07-20 13:00:54 +00:00
|
|
|
"""Test that we can launch an lldb scripted process from the command
|
|
|
|
|
line, check its process ID and read string from memory."""
|
|
|
|
|
self.build()
|
|
|
|
|
target = self.dbg.CreateTarget(self.getBuildArtifact("a.out"))
|
|
|
|
|
self.assertTrue(target, VALID_TARGET)
|
|
|
|
|
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
for module in target.modules:
|
|
|
|
|
if 'a.out' in module.GetFileSpec().GetFilename():
|
|
|
|
|
main_module = module
|
|
|
|
|
|
|
|
|
|
self.assertTrue(main_module, "Invalid main module.")
|
|
|
|
|
error = target.SetModuleLoadAddress(main_module, 0)
|
|
|
|
|
self.assertTrue(error.Success(), "Reloading main module at offset 0 failed.")
|
|
|
|
|
|
2021-07-20 13:00:54 +00:00
|
|
|
scripted_process_example_relpath = ['..','..','..','..','examples','python','scripted_process','my_scripted_process.py']
|
|
|
|
|
self.runCmd("command script import " + os.path.join(self.getSourceDir(),
|
|
|
|
|
*scripted_process_example_relpath))
|
|
|
|
|
|
|
|
|
|
process = target.GetProcess()
|
|
|
|
|
self.assertTrue(process, PROCESS_IS_VALID)
|
|
|
|
|
self.assertEqual(process.GetProcessID(), 42)
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
self.assertEqual(process.GetNumThreads(), 1)
|
2021-07-20 13:00:54 +00:00
|
|
|
|
|
|
|
|
error = lldb.SBError()
|
|
|
|
|
hello_world = "Hello, world!"
|
|
|
|
|
memory_read = process.ReadCStringFromMemory(0x50000000000,
|
|
|
|
|
len(hello_world) + 1, # NULL byte
|
|
|
|
|
error)
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
thread = process.GetSelectedThread()
|
|
|
|
|
self.assertTrue(thread, "Invalid thread.")
|
|
|
|
|
self.assertEqual(thread.GetThreadID(), 0x19)
|
|
|
|
|
self.assertEqual(thread.GetName(), "MyScriptedThread.thread-1")
|
2021-07-20 13:00:54 +00:00
|
|
|
|
[lldb/Plugins] Add memory region support in ScriptedProcess
This patch adds support for memory regions in Scripted Processes.
This is necessary to read the stack memory region in order to
reconstruct each stackframe of the program.
In order to do so, this patch makes some changes to the SBAPI, namely:
- Add a new constructor for `SBMemoryRegionInfo` that takes arguments
such as the memory region name, address range, permissions ...
This is used when reading memory at some address to compute the offset
in the binary blob provided by the user.
- Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList`
to simplify the access to a specific memory region.
With these changes, lldb is now able to unwind the stack and reconstruct
each frame. On top of that, reloading the target module at offset 0 allows
lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an
ordinary Process.
To test this, I wrote a simple program with multiple function calls, ran it in
lldb, stopped at a leaf function and read the registers values and copied
the stack memory into a binary file. These are then used in the python script.
Differential Revision: https://reviews.llvm.org/D108953
Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
2021-10-08 12:25:04 +00:00
|
|
|
self.assertEqual(thread.GetNumFrames(), 4)
|
|
|
|
|
frame = thread.GetSelectedFrame()
|
|
|
|
|
self.assertTrue(frame, "Invalid frame.")
|
|
|
|
|
self.assertEqual(frame.GetFunctionName(), "bar")
|
|
|
|
|
self.assertEqual(int(frame.FindValue("i", lldb.eValueTypeVariableArgument).GetValue()), 42)
|
|
|
|
|
self.assertEqual(int(frame.FindValue("j", lldb.eValueTypeVariableLocal).GetValue()), 42 * 42)
|