<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/lldb/packages/Python/lldbsuite/test/commands, 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>2020-01-15T12:04:04+00:00</updated>
<entry>
<title>[lldb] Add expect_expr function for testing expression evaluation in dotests.</title>
<updated>2020-01-15T12:04:04+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2020-01-15T12:03:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=13f22f5d5958a46db1212a083a426e339204c783'/>
<id>urn:sha1:13f22f5d5958a46db1212a083a426e339204c783</id>
<content type='text'>
Summary:
This patch adds a new function to lldbtest: `expect_expr`. This function is supposed to replace the current approach
of calling `expect`/`runCmd` with `expr`, `p` etc.

`expect_expr` allows evaluating expressions and matching their value/summary/type/error message without
having to do any string matching that might allow unintended passes (e.g., `self.expect("expr 3+4", substrs=["7"])`
can unexpectedly pass for results like `(Class7) $0 = 7`, `(int) $7 = 22`, `(int) $0 = 77` and so on).

This only uses the function in a few places to test and demonstrate it. I'll migrate the tests in follow up commits.

Reviewers: JDevlieghere, shafik, labath

Reviewed By: labath

Subscribers: christof, abidh, lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D70314
</content>
</entry>
<entry>
<title>[lldb/Expression] Improve interpreter error message with a non-running target</title>
<updated>2020-01-14T12:06:58+00:00</updated>
<author>
<name>Med Ismail Bennani</name>
<email>medismail.bennani@gmail.com</email>
</author>
<published>2020-01-14T11:12:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=877723b7ce813d25fc4a358b7d2cb90468733a72'/>
<id>urn:sha1:877723b7ce813d25fc4a358b7d2cb90468733a72</id>
<content type='text'>
When trying to interpret an expression with a function call, if the
process hasn't been launched, the expression fails to be interpreted
and the user gets the following  error message:

```error: Can't run the expression locally```

This message doesn't explain why the expression failed to be
interpreted, that's why this patch improves the error message that is
displayed when trying to run an expression while no process is running.

rdar://11991708

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

Signed-off-by: Med Ismail Bennani &lt;medismail.bennani@gmail.com&gt;
</content>
</entry>
<entry>
<title>[lldb][NFC] Remove debug print statement from TestExprDiagnostics.py</title>
<updated>2020-01-13T13:17:55+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2020-01-13T13:17:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=c1fbede984ec1eb87b35218d3b8161d3a6e92318'/>
<id>urn:sha1:c1fbede984ec1eb87b35218d3b8161d3a6e92318</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[lldb] Mark several tests as not dependent on debug info</title>
<updated>2020-01-13T09:40:29+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2020-01-13T09:00:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=ddf044290ede7d7fd47f4f673e3e628f551a8aac'/>
<id>urn:sha1:ddf044290ede7d7fd47f4f673e3e628f551a8aac</id>
<content type='text'>
Summary:
This just adds `NO_DEBUG_INFO_TESTCASE` to tests that don't really exercise anything debug information specific
and therefore don't need to be rerun for all debug information variants.

Reviewers: labath, jingham, aprantl, mib, jfb

Reviewed By: aprantl

Subscribers: dexonsmith, JDevlieghere, lldb-commits

Tags: #lldb

Differential Revision: https://reviews.llvm.org/D72447
</content>
</entry>
<entry>
<title>[lldb][tests] Cleanup '.categories'</title>
<updated>2020-01-10T13:39:38+00:00</updated>
<author>
<name>Tatyana Krasnukha</name>
<email>tatyana@synopsys.com</email>
</author>
<published>2019-12-11T16:33:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=b3af8ab7f83c2a825c584ddedf5cc9207ca66b44'/>
<id>urn:sha1:b3af8ab7f83c2a825c584ddedf5cc9207ca66b44</id>
<content type='text'>
</content>
</entry>
<entry>
<title>[lldb] Fix that TestNoSuchArch.py was passing for the wrong reason</title>
<updated>2020-01-09T11:09:48+00:00</updated>
<author>
<name>Raphael Isemann</name>
<email>teemperor@gmail.com</email>
</author>
<published>2020-01-09T11:09:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=782ad91cc423bf602718e2bf9ffc59e55350463f'/>
<id>urn:sha1:782ad91cc423bf602718e2bf9ffc59e55350463f</id>
<content type='text'>
The command here failed due to the type in 'create' but the expect
did not actually check for the error message. This fixes the typo
and adds a check for the actuall error message we should see.
</content>
</entry>
<entry>
<title>Change the patterns to include the prefix '= ' so we don't pass errantly.</title>
<updated>2020-01-06T23:20:13+00:00</updated>
<author>
<name>Jason Molenda</name>
<email>jmolenda@apple.com</email>
</author>
<published>2020-01-06T23:18:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=450073c639d7f182e48ec8b1b588212194089a52'/>
<id>urn:sha1:450073c639d7f182e48ec8b1b588212194089a52</id>
<content type='text'>
Looking at a sometimes-passing test case on a platform
where random values were being returned - sometimes
the expected digit ('1' or '2') would be included in the
random returned value.  Add a prefix to reduce the likelihood of
this a bit.
</content>
</entry>
<entry>
<title>[lldb/Command] Add --force option for `watchpoint delete` command</title>
<updated>2020-01-04T02:11:15+00:00</updated>
<author>
<name>Med Ismail Bennani</name>
<email>medismail.bennani@gmail.com</email>
</author>
<published>2019-12-28T13:47:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=df71f92fbb7c96cfd36d247ae6fb6929cb9bce35'/>
<id>urn:sha1:df71f92fbb7c96cfd36d247ae6fb6929cb9bce35</id>
<content type='text'>
Currently, there is no option to delete all the watchpoint without LLDB
asking for a confirmation. Besides making the watchpoint delete command
homogeneous with the breakpoint delete command, this option could also
become handy to trigger automated watchpoint deletion i.e. using
breakpoint actions.

rdar://42560586

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

Signed-off-by: Med Ismail Bennani &lt;medismail.bennani@gmail.com&gt;
</content>
</entry>
<entry>
<title>Revert "[lldb/Command] Add --force option for `watchpoint delete` command"</title>
<updated>2020-01-03T01:14:45+00:00</updated>
<author>
<name>Med Ismail Bennani</name>
<email>medismail.bennani@gmail.com</email>
</author>
<published>2020-01-03T01:14:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=4117c8c0194cdf59e229f6826e0908eb3f2bcfc6'/>
<id>urn:sha1:4117c8c0194cdf59e229f6826e0908eb3f2bcfc6</id>
<content type='text'>
This reverts commit 3620e5f28a4d2800fb6c325ec24b3d660e48b9ba.
</content>
</entry>
<entry>
<title>[lldb/Command] Add --force option for `watchpoint delete` command</title>
<updated>2020-01-03T00:51:22+00:00</updated>
<author>
<name>Med Ismail Bennani</name>
<email>medismail.bennani@gmail.com</email>
</author>
<published>2019-12-28T13:47:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=3620e5f28a4d2800fb6c325ec24b3d660e48b9ba'/>
<id>urn:sha1:3620e5f28a4d2800fb6c325ec24b3d660e48b9ba</id>
<content type='text'>
Currently, there is no option to delete all the watchpoint without LLDB
asking for a confirmation. Besides making the watchpoint delete command
homogeneous with the breakpoint delete command, this option could also
become handy to trigger automated watchpoint deletion i.e. using
breakpoint actions.

rdar://42560586

Signed-off-by: Med Ismail Bennani &lt;medismail.bennani@gmail.com&gt;
</content>
</entry>
</feed>
