<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/lldb/packages/Python/lldbsuite/test/functionalities/step_scripted, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2019-10-03T22:50:18+00:00</updated>
<entry>
<title>Pass an SBStructuredData to scripted ThreadPlans on use.</title>
<updated>2019-10-03T22:50:18+00:00</updated>
<author>
<name>Jim Ingham</name>
<email>jingham@apple.com</email>
</author>
<published>2019-10-03T22:50:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=27a14f19c810f494adddb8aaff960336ab4492e7'/>
<id>urn:sha1:27a14f19c810f494adddb8aaff960336ab4492e7</id>
<content type='text'>
This will allow us to write reusable scripted ThreadPlans, since
you can use key/value pairs with known keys in the plan to parametrize
its behavior.

Differential Revision: https://reviews.llvm.org/D68366

llvm-svn: 373675
</content>
</entry>
<entry>
<title>Allow the internal-state-thread free access to the TargetAPI mutex.</title>
<updated>2019-10-01T00:47:25+00:00</updated>
<author>
<name>Jim Ingham</name>
<email>jingham@apple.com</email>
</author>
<published>2019-10-01T00:47:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=58c3235ee976e577ab183a3058e804f4ac1ae027'/>
<id>urn:sha1:58c3235ee976e577ab183a3058e804f4ac1ae027</id>
<content type='text'>
It is always doing work on behalf of another thread that presumably
has the mutex, so if it is calling SB API's it should have free access
to the mutex.  This is the same decision as we made earlier with the
process RunLock.

Differential Revision: https://reviews.llvm.org/D68174

llvm-svn: 373280
</content>
</entry>
<entry>
<title>Give an error when StepUsingScriptedThreadPlan is passed a bad classname.</title>
<updated>2019-09-28T00:53:45+00:00</updated>
<author>
<name>Jim Ingham</name>
<email>jingham@apple.com</email>
</author>
<published>2019-09-28T00:53:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=93c98346e98a50e481efda95c9b095bf2b1c8a73'/>
<id>urn:sha1:93c98346e98a50e481efda95c9b095bf2b1c8a73</id>
<content type='text'>
Differential Revision: https://reviews.llvm.org/D68173

llvm-svn: 373135
</content>
</entry>
<entry>
<title>[dotest] Avoid the need for LEVEL= makefile boilerplate</title>
<updated>2019-09-04T07:46:25+00:00</updated>
<author>
<name>Pavel Labath</name>
<email>pavel@labath.sk</email>
</author>
<published>2019-09-04T07:46:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=418a272f4ab4221c37a9272d48fd31d5ac1bddc1'/>
<id>urn:sha1:418a272f4ab4221c37a9272d48fd31d5ac1bddc1</id>
<content type='text'>
Summary:
Instead of each test case knowing its depth relative to the test root,
we can just have dotest add the folder containing Makefile.rules to the
include path.

This was motivated by r370616, though I have been wanting to do this
ever since we moved to building tests out-of-tree.

The only manually modified files in this patch are lldbinline.py and
plugins/builder_base.py. The rest of the patch has been produced by this
shell command:
  find . \( -name Makefile -o -name '*.mk' \)  -exec sed --in-place -e '/LEVEL *:\?=/d' -e '1,2{/^$/d}' -e 's,\$(LEVEL)/,,' {} +

Reviewers: teemperor, aprantl, espindola, jfb

Subscribers: emaste, javed.absar, arichardson, christof, arphaman, lldb-commits

Differential Revision: https://reviews.llvm.org/D67083

llvm-svn: 370845
</content>
</entry>
<entry>
<title>Add setting to require hardware breakpoints.</title>
<updated>2018-11-15T01:18:15+00:00</updated>
<author>
<name>Jonas Devlieghere</name>
<email>jonas@devlieghere.com</email>
</author>
<published>2018-11-15T01:18:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=e103ae92ef2336854587778bd3ae88a87e409a5e'/>
<id>urn:sha1:e103ae92ef2336854587778bd3ae88a87e409a5e</id>
<content type='text'>
When debugging read-only memory we cannot use software breakpoint. We
already have support for hardware breakpoints and users can specify them
with `-H`. However, there's no option to force LLDB to use hardware
breakpoints internally, for example while stepping.

This patch adds a setting target.require-hardware-breakpoint that forces
LLDB to always use hardware breakpoints. Because hardware breakpoints
are a limited resource and can fail to resolve, this patch also extends
error handling in thread plans, where breakpoints are used for stepping.

Differential revision: https://reviews.llvm.org/D54221

llvm-svn: 346920
</content>
</entry>
<entry>
<title>[API] Extend the `SBThreadPlan` interface</title>
<updated>2018-10-25T08:27:42+00:00</updated>
<author>
<name>Aleksandr Urakov</name>
<email>aleksandr.urakov@jetbrains.com</email>
</author>
<published>2018-10-25T08:27:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=c1c0fac76595da4a46db30da68e8444b9d1e3521'/>
<id>urn:sha1:c1c0fac76595da4a46db30da68e8444b9d1e3521</id>
<content type='text'>
Summary:
This patch extends the `SBThreadPlan` to allow retrieving of thread plans
for scripted steps.

Reviewers: labath, zturner, jingham

Reviewed By: jingham

Subscribers: lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D53361

llvm-svn: 345247
</content>
</entry>
</feed>
