<?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 Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><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/Makefile#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/Makefile</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>
