<?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 BreakpointBase.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/BreakpointBase.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/BreakpointBase.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/BreakpointBase.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/BreakpointBase.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>d58c128bc42b8a9cc45516ba9fe9e6a3c322d7b3 - [lldb-dap][NFC] Add Breakpoint struct to share common logic. (#80753)</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#d58c128bc42b8a9cc45516ba9fe9e6a3c322d7b3</link>
        <description>[lldb-dap][NFC] Add Breakpoint struct to share common logic. (#80753)This adds a layer between `SounceBreakpoint`/`FunctionBreakpoint` and`BreakpointBase` to have better separation and encapsulation so we arenot directly operating on `SBBreakpoint`.I basically moved the `SBBreakpoint` and the methods that requires itfrom `BreakpointBase` to `Breakpoint`. This allows adding support fordata watchpoint easier by sharing the logic inside `BreakpointBase`.

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Tue, 13 Feb 2024 16:38:02 +0000</pubDate>
        <dc:creator>Zequan Wu &lt;zequanwu@google.com&gt;</dc:creator>
    </item>
<item>
        <title>ffd173ba0b4a6d84f45308e78cea4af611bec10e - [lldb-dap] Emit more structured info along with variables (#75244)</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#ffd173ba0b4a6d84f45308e78cea4af611bec10e</link>
        <description>[lldb-dap] Emit more structured info along with variables (#75244)In order to allow smarter vscode extensions, it&apos;s useful to sendadditional structured information of SBValues to the client.Specifically, I&apos;m now sending error, summary, autoSummary andinMemoryValue in addition to the existing properties being sent. This ischeap because these properties have to be calculated anyway to generatethe display value of the variable, but they are now available forextensions to better analyze variables. For example, if the error fieldis not present, the extension might be able to provide cool features,and the current way to do that is to look for the `&quot;&lt;error: &quot;` prefix,which is error-prone.This also incorporates a tiny feedback fromhttps://github.com/llvm/llvm-project/pull/74865#issuecomment-1850695477

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Tue, 02 Jan 2024 18:06:13 +0000</pubDate>
        <dc:creator>Walter Erquinigo &lt;a20012251@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>f175b9647ccdfd67300264b2d3bd76e6f9a3fb93 - Improve VSCode DAP logpoint value summary (#71723)</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#f175b9647ccdfd67300264b2d3bd76e6f9a3fb93</link>
        <description>Improve VSCode DAP logpoint value summary (#71723)Currently VSCode logpoint uses `SBValue::GetValue` to get the value forprinting. This is not providing an intuitive result for std::string orchar * -- it shows the pointer value instead of the string content.This patch improves by prefers `SBValue::GetSummary()` before using`SBValue::GetValue()`.---------Co-authored-by: jeffreytan81 &lt;jeffreytan@fb.com&gt;

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Thu, 09 Nov 2023 00:48:55 +0000</pubDate>
        <dc:creator>jeffreytan81 &lt;jeffreytan@meta.com&gt;</dc:creator>
    </item>
<item>
        <title>01263c6c6fb495a94fe0ccbb1420bb1ec8460748 - [lldb] Rename lldb-vscode to lldb-dap (#69264)</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#01263c6c6fb495a94fe0ccbb1420bb1ec8460748</link>
        <description>[lldb] Rename lldb-vscode to lldb-dap (#69264)Rename lldb-vscode to lldb-dap. This change is largely mechanical. Thefollowing substitutions cover the majority of the changes in thiscommit:  s/VSCODE/DAP/  s/VSCode/DAP/  s/vscode/dap/  s/g_vsc/g_dap/Discourse RFC:https://discourse.llvm.org/t/rfc-rename-lldb-vscode-to-lldb-dap/74075/

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Thu, 19 Oct 2023 16:48:54 +0000</pubDate>
        <dc:creator>Jonas Devlieghere &lt;jonas@devlieghere.com&gt;</dc:creator>
    </item>
<item>
        <title>58e9cc13e24f668a33abdae201d59a02e10c22c0 - Revert &quot;[lldb] Remove redundant .c_str() and .get() calls&quot;</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#58e9cc13e24f668a33abdae201d59a02e10c22c0</link>
        <description>Revert &quot;[lldb] Remove redundant .c_str() and .get() calls&quot;This reverts commit fbaf48be0ff6fb24b9aa8fe9c2284fe88a8798dd.This has broken all LLDB buildbots:https://lab.llvm.org/buildbot/#/builders/68/builds/44990https://lab.llvm.org/buildbot/#/builders/96/builds/33160

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Mon, 19 Dec 2022 08:50:31 +0000</pubDate>
        <dc:creator>Muhammad Omair Javaid &lt;omair.javaid@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>fbaf48be0ff6fb24b9aa8fe9c2284fe88a8798dd - [lldb] Remove redundant .c_str() and .get() calls</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#fbaf48be0ff6fb24b9aa8fe9c2284fe88a8798dd</link>
        <description>[lldb] Remove redundant .c_str() and .get() callsRemoving .c_str() has a semantics difference, but the use scenarioslikely do not matter as we don&apos;t have NUL in the strings.

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Sun, 18 Dec 2022 01:15:25 +0000</pubDate>
        <dc:creator>Fangrui Song &lt;i@maskray.me&gt;</dc:creator>
    </item>
<item>
        <title>6c8995649afac04a9eb0e71affd997e493c9b93a - Add formatting support for VSCode logpoints message</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#6c8995649afac04a9eb0e71affd997e493c9b93a</link>
        <description>Add formatting support for VSCode logpoints messagehttps://reviews.llvm.org/D127702 adds the initial logpoints support inlldb-vscode. This patch further improves it by:1. Adding a newline at the end of each log message2. Support most of the format specifiers like \t, \n, \x etc..The implementation is borrowed from FormatEntity::ParseInternal(). Futurepatch should merge these two implementations.Differential Revision: https://reviews.llvm.org/D136697

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Tue, 25 Oct 2022 16:42:34 +0000</pubDate>
        <dc:creator>Jeffrey Tan &lt;jeffreytan@fb.com&gt;</dc:creator>
    </item>
<item>
        <title>5109de2da2e2b2321bd2bc504a3ddcedce51c0f8 - Fix build break introduced by https://reviews.llvm.org/D127702</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#5109de2da2e2b2321bd2bc504a3ddcedce51c0f8</link>
        <description>Fix build break introduced by https://reviews.llvm.org/D127702Fix build break introduced by https://reviews.llvm.org/D127702Differential Revision: https://reviews.llvm.org/D128234

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Tue, 21 Jun 2022 00:21:18 +0000</pubDate>
        <dc:creator>Jeffrey Tan &lt;jeffreytan@fb.com&gt;</dc:creator>
    </item>
<item>
        <title>8c6e138aa893bb88fc3d5d449e42082741f0e2a2 - Support logpoints in lldb-vscode</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#8c6e138aa893bb88fc3d5d449e42082741f0e2a2</link>
        <description>Support logpoints in lldb-vscodeThis patch implements VSCode DAP logpoints feature (also called tracepointin other VS debugger).This will provide a convenient way for user to do printf style loggingdebugging without pausing debuggee.Differential Revision: https://reviews.llvm.org/D127702

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Fri, 13 May 2022 18:31:23 +0000</pubDate>
        <dc:creator>Jeffrey Tan &lt;jeffreytan@fb.com&gt;</dc:creator>
    </item>
<item>
        <title>9cb227f561f4e5491840694580abbe7c0123b358 - Stop emitting a breakpoint for each location in a breakpoint when responding to breakpoint commands.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#9cb227f561f4e5491840694580abbe7c0123b358</link>
        <description>Stop emitting a breakpoint for each location in a breakpoint when responding to breakpoint commands.Summary: The VS Code DAP expects on response for each breakpoint that was requested. If we responsd with multiple entries for one breakpoint the VS Code UI gets out of date. Currently the VS code DAP doesn&apos;t handle one breakpoint with multiple locations. If this ever gets fixed we can modify our code.Reviewers: labathSubscribers: lldb-commitsTags: #lldbDifferential Revision: https://reviews.llvm.org/D73665

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Wed, 29 Jan 2020 22:11:40 +0000</pubDate>
        <dc:creator>Greg Clayton &lt;gclayton@fb.com&gt;</dc:creator>
    </item>
<item>
        <title>adcd02683856c30ba6f349279509acecd90063df - Make llvm::StringRef to std::string conversions explicit.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#adcd02683856c30ba6f349279509acecd90063df</link>
        <description>Make llvm::StringRef to std::string conversions explicit.This is how it should&apos;ve been and brings it more in line withstd::string_view. There should be no functional change here.This is mostly mechanical from a custom clang-tidy check, with a lot ofmanual fixups. It uncovers a lot of minor inefficiencies.This doesn&apos;t actually modify StringRef yet, I&apos;ll do that in a follow-up.

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Tue, 28 Jan 2020 19:23:46 +0000</pubDate>
        <dc:creator>Benjamin Kramer &lt;benny.kra@googlemail.com&gt;</dc:creator>
    </item>
<item>
        <title>2946cd701067404b99c39fb29dc9c74bd7193eb3 - Update the file headers across all of the LLVM projects in the monorepo</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#2946cd701067404b99c39fb29dc9c74bd7193eb3</link>
        <description>Update the file headers across all of the LLVM projects in the monorepoto reflect the new license.We understand that people may be surprised that we&apos;re moving the headerentirely to discuss the new license. We checked this carefully with theFoundation&apos;s lawyer and we believe this is the correct approach.Essentially, all code in the project is now made available by the LLVMproject under our new license, so you will see that the license headersinclude that license only. Some of our contributors have contributedcode under our old license, and accordingly, we have retained a copy ofour old license notice in the top-level files in each project andrepository.llvm-svn: 351636

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Sat, 19 Jan 2019 08:50:56 +0000</pubDate>
        <dc:creator>Chandler Carruth &lt;chandlerc@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>2f5cf8511a3f0ad97db2acf51c6c9ea0ddc9da92 - Add a new tool named &quot;lldb-vscode&quot; that implements the Visual Studio Code Debug Adaptor Protocol</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp#2f5cf8511a3f0ad97db2acf51c6c9ea0ddc9da92</link>
        <description>Add a new tool named &quot;lldb-vscode&quot; that implements the Visual Studio Code Debug Adaptor ProtocolThis patch adds a new lldb-vscode tool that speaks the Microsoft Visual Studio Code debug adaptor protocol. It has full unit tests that test all packets.This tool can be easily packaged up into a native extension and used with Visual Studio Code, and it can also be used by NuclideDifferential Revision: https://reviews.llvm.org/D50365llvm-svn: 339911

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/BreakpointBase.cpp</description>
        <pubDate>Thu, 16 Aug 2018 17:59:38 +0000</pubDate>
        <dc:creator>Greg Clayton &lt;gclayton@apple.com&gt;</dc:creator>
    </item>
</channel>
</rss>
