<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in TestObjCRecognizer.py</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>9c2468821ec51defd09c246fea4a47886fff8c01 - [lldb][test] Modernize asserts (#82503)</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/test/API/macosx/objc_exception_recognizer/TestObjCRecognizer.py#9c2468821ec51defd09c246fea4a47886fff8c01</link>
        <description>[lldb][test] Modernize asserts (#82503)This uses [teyit](https://pypi.org/project/teyit/) to modernize asserts,as recommended by the [unittest releasenotes](https://docs.python.org/3.12/whatsnew/3.12.html#id3).For example, `assertTrue(a == b)` is replaced with `assertEqual(a, b)`.This produces better error messages, e.g. `error: unexpectedly found 1and 2 to be different` instead of `error: False`.

            List of files:
            /llvm-project/lldb/test/API/macosx/objc_exception_recognizer/TestObjCRecognizer.py</description>
        <pubDate>Wed, 21 Feb 2024 19:02:30 +0000</pubDate>
        <dc:creator>Jordan Rupprecht &lt;rupprecht@google.com&gt;</dc:creator>
    </item>
<item>
        <title>2238dcc39358353cac21df75c3c3286ab20b8f53 - [NFC][Py Reformat] Reformat python files in lldb</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/test/API/macosx/objc_exception_recognizer/TestObjCRecognizer.py#2238dcc39358353cac21df75c3c3286ab20b8f53</link>
        <description>[NFC][Py Reformat] Reformat python files in lldbThis is an ongoing series of commits that are reformatting our Pythoncode. Reformatting is done with `black` (23.1.0).If you end up having problems merging this commit because you have madechanges to a python file, the best way to handle that is to run `gitcheckout --ours &lt;yourfile&gt;` and then reformat it with black.RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-styleDifferential revision: https://reviews.llvm.org/D151460

            List of files:
            /llvm-project/lldb/test/API/macosx/objc_exception_recognizer/TestObjCRecognizer.py</description>
        <pubDate>Thu, 25 May 2023 15:48:57 +0000</pubDate>
        <dc:creator>Jonas Devlieghere &lt;jonas@devlieghere.com&gt;</dc:creator>
    </item>
<item>
        <title>f79c037b63278bc5b4481a1a55c68e42f0ea1461 - Fix the check in StopInfoBreakpoint for &quot;are we currently running an expression&quot;</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/test/API/macosx/objc_exception_recognizer/TestObjCRecognizer.py#f79c037b63278bc5b4481a1a55c68e42f0ea1461</link>
        <description>Fix the check in StopInfoBreakpoint for &quot;are we currently running an expression&quot;We were checking &quot;WasTheLastResumeForUserExpression&quot; but that returns true evenif that expression was completed, provided we haven&apos;t run again.  This uses abetter check.This is actually fairly hard to trigger.  It happens the first time you hit anobjc_exception_throw breakpoint and invoke that frame recognizer for that.  ButI couldn&apos;t trigger it using a Python based frame recognizer.  So I wrote a testfor the objc_exception_throw_breakpoint recognizer which should have been thereanyway...  It fails (the target auto-continues) w/o this patch and succeeds withit.Differential Revision: https://reviews.llvm.org/D147587

            List of files:
            /llvm-project/lldb/test/API/macosx/objc_exception_recognizer/TestObjCRecognizer.py</description>
        <pubDate>Thu, 06 Apr 2023 00:10:42 +0000</pubDate>
        <dc:creator>Jim Ingham &lt;jingham@apple.com&gt;</dc:creator>
    </item>
</channel>
</rss>
