<?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 InstructionBreakpoint.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>b99d4112585302cbd01f9b851a04adc6e4fb5218 - [lldb-dap] Refactoring breakpoints to not use the `g_dap` reference. (#115208)</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/InstructionBreakpoint.cpp#b99d4112585302cbd01f9b851a04adc6e4fb5218</link>
        <description>[lldb-dap] Refactoring breakpoints to not use the `g_dap` reference. (#115208)Refactoring breakpoints to not use the `g_dap` reference.Instead, when a breakpoint is constructed it will be passed a DAPreference that it should use for its lifetime.This is part of a larger refactor to remove the global `g_dap` variableto allow us to create multiple DAP instances.---------Co-authored-by: Pavel Labath &lt;pavel@labath.sk&gt;

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/InstructionBreakpoint.cpp</description>
        <pubDate>Fri, 08 Nov 2024 21:36:25 +0000</pubDate>
        <dc:creator>John Harrison &lt;harjohn@google.com&gt;</dc:creator>
    </item>
<item>
        <title>09c258ef6a2fcca2161488b214d53ef39891fa22 - [NFC][lldb-dap] Clean-up includes (#113839)</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/InstructionBreakpoint.cpp#09c258ef6a2fcca2161488b214d53ef39891fa22</link>
        <description>[NFC][lldb-dap] Clean-up includes (#113839)This commit cleans up the includes in the `lldb-dap` subfolder. The mainmotivation was that I got annoyed by `clangd` always complaining aboutunused includes while working on lldb-dap.

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/InstructionBreakpoint.cpp</description>
        <pubDate>Mon, 28 Oct 2024 10:01:57 +0000</pubDate>
        <dc:creator>Adrian Vogelsgesang &lt;avogelsgesang@salesforce.com&gt;</dc:creator>
    </item>
<item>
        <title>89c27d6b07dd03a71e5692caa4e20ab14f948921 - [lldb-dap] Enabling instruction breakpoint support to lldb-dap. (#105278)</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/InstructionBreakpoint.cpp#89c27d6b07dd03a71e5692caa4e20ab14f948921</link>
        <description>[lldb-dap] Enabling instruction breakpoint support to lldb-dap. (#105278)Added support for &quot;supportsInstructionBreakpoints&quot; capability and now itthis command is triggered when we set instruction breakpoint.We need this support as part of enabling disassembly view debugging.Following features should work as part of this feature enablement:1. Settings breakpoints in disassembly view: Unsetting the breakpoint isnot happening from the disassembly view. Currently we need to unsetbreakpoint manually from the breakpoint List. Multiple breakpoints aregetting set for the same $2. Step over, step into, continue in the disassembly viewThe format for DisassembleRequest and DisassembleResponse athttps://raw.githubusercontent.com/microsoft/vscode/master/src/vs/workbench/contrib/debug/common/debugProtocol.d.ts.Ref Images:Set instruction breakpoint in disassembly view:![image](https://github.com/user-attachments/assets/833bfb34-86f4-40e2-8c20-14b638a612a2)After issuing continue:![image](https://github.com/user-attachments/assets/884572a3-915e-422b-b8dd-d132e5c00de6)---------Co-authored-by: Santhosh Kumar Ellendula &lt;sellendu@hu-sellendu-hyd.qualcomm.com&gt;Co-authored-by: Santhosh Kumar Ellendula &lt;sellendu@hu-sellendu-lv.qualcomm.com&gt;

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/InstructionBreakpoint.cpp</description>
        <pubDate>Mon, 26 Aug 2024 18:49:39 +0000</pubDate>
        <dc:creator>Santhosh Kumar Ellendula &lt;quic_sellendu@quicinc.com&gt;</dc:creator>
    </item>
</channel>
</rss>
