<?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 IOStream.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><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/IOStream.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/IOStream.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>744f38913fa380580431df0ae89ef5fb3df30240 - [lldb] Use StringRef::{starts,ends}_with (NFC)</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/IOStream.cpp#744f38913fa380580431df0ae89ef5fb3df30240</link>
        <description>[lldb] Use StringRef::{starts,ends}_with (NFC)This patch replaces uses of StringRef::{starts,ends}with withStringRef::{starts,ends}_with for consistency withstd::{string,string_view}::{starts,ends}_with in C++20.I&apos;m planning to deprecate and eventually removeStringRef::{starts,ends}with.

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/IOStream.cpp</description>
        <pubDate>Sat, 16 Dec 2023 22:39:37 +0000</pubDate>
        <dc:creator>Kazu Hirata &lt;kazu@google.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/IOStream.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/IOStream.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>24f9a2f53db78df59761f46ceed3bb5e7aa0d331 - [LLDB] Applying clang-tidy modernize-use-equals-default over LLDB</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/IOStream.cpp#24f9a2f53db78df59761f46ceed3bb5e7aa0d331</link>
        <description>[LLDB] Applying clang-tidy modernize-use-equals-default over LLDBApplied modernize-use-equals-default clang-tidy check over LLDB.This check is already present in the lldb/.clang-tidy config.Differential Revision: https://reviews.llvm.org/D121844

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/IOStream.cpp</description>
        <pubDate>Thu, 31 Mar 2022 20:20:46 +0000</pubDate>
        <dc:creator>Shafik Yaghmour &lt;syaghmour@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>64f47c1e58a10de160ce3fb3afbc50c0243e2977 - [lldb-vscode] redirect stderr/stdout to the IDE&apos;s console</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/IOStream.cpp#64f47c1e58a10de160ce3fb3afbc50c0243e2977</link>
        <description>[lldb-vscode] redirect stderr/stdout to the IDE&apos;s consoleIn certain occasions times, like when LLDB is initializing andevaluating the .lldbinit files, it tries to print to stderr and stdoutdirectly. This confuses the IDE with malformed data, as it talks tolldb-vscode using stdin and stdout following the JSON RPC protocol. Thisends up terminating the debug session with the user unaware of what&apos;sgoing on. There might be other situations in which this can happen, andthey will be harder to debug than the .lldbinit case.After several discussions with @clayborg, @yinghuitan and @aadsm, werealized that the best course of action is to simply redirect stdout andstderr to the console, without modifying LLDB itself. This will prove tobe resilient to future bugs or features.I made the simplest possible redirection logic I could come up with. Itonly works for POSIX, and to make it work with Windows should be merelychanging pipe and dup2 for the windows equivalents like _pipe and _dup2.Sadly I don&apos;t have a Windows machine, so I&apos;ll do it later once my officereopens, or maybe someone else can do it.I&apos;m intentionally not adding a stop-redirecting logic, as I don&apos;t see ituseful for the lldb-vscode case (why would we want to do that, really?).I added a test.Note: this is a simpler version of D80659. I first tried to implement aRIIA version of it, but it was problematic to manage the state of thethread and reverting the redirection came with some non trivialcomplexities, like what to do with unflushed data after the debugsession has finished on the IDE&apos;s side.

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/IOStream.cpp</description>
        <pubDate>Wed, 21 Apr 2021 21:20:17 +0000</pubDate>
        <dc:creator>Walter Erquinigo &lt;a20012251@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>36496cc2992d6fa26e6024971efcfc7d15f69888 - [lldb-vscode] correctly use Windows macros</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/IOStream.cpp#36496cc2992d6fa26e6024971efcfc7d15f69888</link>
        <description>[lldb-vscode] correctly use Windows macros@mstorsjo found a mistake that I made when trying to fix some Windowscompilation errors encountered by @stella.stamenova.I was incorrectly using the LLVM_ON_UNIX macro. In any case, proper useof  #if defined(_WIN32)should be the actual fix.Differential Revision: https://reviews.llvm.org/D96060

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/IOStream.cpp</description>
        <pubDate>Thu, 04 Feb 2021 18:07:07 +0000</pubDate>
        <dc:creator>Walter Erquinigo &lt;a20012251@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>0bca9a7ce2eeaa9f1d732ffbc17769560a2b236e - Fix lldb-vscode builds on Windows targeting POSIX</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/IOStream.cpp#0bca9a7ce2eeaa9f1d732ffbc17769560a2b236e</link>
        <description>Fix lldb-vscode builds on Windows targeting POSIX@stella.stamenova found out that lldb-vscode&apos;s Win32 macros were failingwhen building on windows targetings POSIX platforms.I&apos;m changing these macros for LLVM_ON_UNIX, which should be moreaccurate.

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/IOStream.cpp</description>
        <pubDate>Thu, 28 Jan 2021 17:24:30 +0000</pubDate>
        <dc:creator>Walter Erquinigo &lt;a20012251@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d0ac1888aab490589788bd51a9f44f7745dc5819 - [lldb] Handle EOF from `lldb-vscode`</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/IOStream.cpp#d0ac1888aab490589788bd51a9f44f7745dc5819</link>
        <description>[lldb] Handle EOF from `lldb-vscode`Sometimes (when running lldb-vscode under strace) I get:read(0, &quot;&quot;, 16)                         = 0read(0, &quot;&quot;, 16)                         = 0read(0, &quot;&quot;, 16)                         = 0...With this patch testcases finish properly even with strace:read(0, &quot;&quot;, 16)                         = 0futex(0x1346508, FUTEX_WAKE_PRIVATE, 2147483647) = 0stat(&quot;&quot;, 0x7ffe8f2634c8)                = -1 ENOENT (No such file or directory)--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=9124, si_uid=1001, si_status=SIGINT, si_utime=1, si_stime=0} ---close(4)                                = 0exit_group(0)                           = ?+++ exited with 0 +++Differential Revision: https://reviews.llvm.org/D64698llvm-svn: 366187

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/IOStream.cpp</description>
        <pubDate>Tue, 16 Jul 2019 06:34:44 +0000</pubDate>
        <dc:creator>Jan Kratochvil &lt;jan.kratochvil@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>fee5576f7cd76f4b03a2549088f4fab9f5a80462 - [lldb-vscode] Fix warning</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/IOStream.cpp#fee5576f7cd76f4b03a2549088f4fab9f5a80462</link>
        <description>[lldb-vscode] Fix warningI changed the variable to an unsigned to get rid of a signed andunsigned compare without realizing the value could be negative. Thisfixes the assert instead.llvm-svn: 355708

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/IOStream.cpp</description>
        <pubDate>Fri, 08 Mar 2019 17:36:54 +0000</pubDate>
        <dc:creator>Jonas Devlieghere &lt;jonas@devlieghere.com&gt;</dc:creator>
    </item>
<item>
        <title>8d359c147de6e4da76fabf20faeafd3f3a9c6b34 - Make bytes_read an unsigned</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/IOStream.cpp#8d359c147de6e4da76fabf20faeafd3f3a9c6b34</link>
        <description>Make bytes_read an unsignedllvm-svn: 355651

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/IOStream.cpp</description>
        <pubDate>Thu, 07 Mar 2019 22:59:55 +0000</pubDate>
        <dc:creator>Jonas Devlieghere &lt;jonas@devlieghere.com&gt;</dc:creator>
    </item>
<item>
        <title>29e8754172031ed217d25e3de0bc4047192a3453 - [lldb-vscode] Support running in server mode on Windows.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lldb/tools/lldb-vscode/IOStream.cpp#29e8754172031ed217d25e3de0bc4047192a3453</link>
        <description>[lldb-vscode] Support running in server mode on Windows.Windows can&apos;t use standard i/o system calls such as read and writeto work with sockets, it instead needs to use the specific sendand recv calls.  This complicates matters for the debug adapter,since it needs to be able to work in both server mode where itcommunicates over a socket, as well as non-server mode where itcommunicates via stdin and stdout.  To abstract this out, I&apos;veintroduced a class IOStream which hides all these details andexposes a read/write interface that does the right on eachplatform.Differential Revision: https://reviews.llvm.org/D59104llvm-svn: 355637

            List of files:
            /llvm-project/lldb/tools/lldb-vscode/IOStream.cpp</description>
        <pubDate>Thu, 07 Mar 2019 21:23:21 +0000</pubDate>
        <dc:creator>Zachary Turner &lt;zturner@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
