2c76e88e9e
The idea behind the address-expression is that it handles all the common
expressions that produce addresses. It handles actual valid expressions
that return a scalar, and it handles useful cases that the various
source languages don't support. At present, the fallback handles:
<symbol_name>{+-}<offset>
which isn't valid C but is very handy.
This patch adds handling of:
$<reg_name>
and
$<reg_name>{+-}<offset>
That's kind of pointless in C because the C expression parser handles
that expression already. But some languages don't have a straightforward
way to represent register values like this (swift) so having this
fallback is quite a quality of life improvement.
I added a test which tests that I didn't mess up either of these
fallbacks, though it doesn't test the actually handling of registers
that I added, since the expression parser for C succeeds in that case
and returns before this code gets run.
I will add a test on the swift fork for that checks that this works the
same way for a swift frame after this check.
28 lines
840 B
Python
28 lines
840 B
Python
"""
|
|
Make sure that "target modules lookup -va $pc" works
|
|
"""
|
|
|
|
|
|
import lldb
|
|
import lldbsuite.test.lldbutil as lldbutil
|
|
from lldbsuite.test.lldbtest import *
|
|
|
|
|
|
class TestImageLookupPCInC(TestBase):
|
|
def test_sample_rename_this(self):
|
|
"""There can be many tests in a test case - describe this test here."""
|
|
self.build()
|
|
self.main_source_file = lldb.SBFileSpec("main.c")
|
|
self.sample_test()
|
|
|
|
def sample_test(self):
|
|
"""Make sure the address expression resolves to the right function"""
|
|
|
|
(target, process, thread, bkpt) = lldbutil.run_to_source_breakpoint(
|
|
self, "Set a breakpoint here", self.main_source_file
|
|
)
|
|
|
|
self.expect("target modules lookup -va $pc", substrs=["doSomething"])
|
|
self.expect("target modules lookup -va $pc+4", substrs=["doSomething"])
|
|
|