[Lldb-commits] [lldb] 64df8f8 - [lldb][test] Fix TestEmptyFuncThreadStepOut.py (#161788)

2025-10-21 Thread via lldb-commits
Author: Igor Kudrin Date: 2025-10-21T20:01:08-07:00 New Revision: 64df8f83fe293b6c08477975cbb4451c76b51c54 URL: https://github.com/llvm/llvm-project/commit/64df8f83fe293b6c08477975cbb4451c76b51c54 DIFF: https://github.com/llvm/llvm-project/commit/64df8f83fe293b6c08477975cbb4451c76b51c54.diff L

[Lldb-commits] [lldb] [lldb][test] Fix TestEmptyFuncThreadStepOut.py (PR #161788)

2025-10-21 Thread Igor Kudrin via lldb-commits
https://github.com/igorkudrin closed https://github.com/llvm/llvm-project/pull/161788 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [clang] [clang-tools-extra] [lldb] [clang] Don't silently inherit the VFS from `FileManager` (PR #164323)

2025-10-21 Thread Jan Svoboda via lldb-commits
jansvoboda11 wrote: You can set these separately based on your needs. If you look at `cc1_main()`, it only sets the VFS, but not the `FileManger`. There are situations, where the `FileManager` is set later, for example when loading an `ASTUnit`. Similarly, `SourceManager` is not always needed

[Lldb-commits] [lldb] [lldb] Implement ProcessGDBRemote support for ReadMemoryRanges (PR #164311)

2025-10-21 Thread Jason Molenda via lldb-commits
@@ -45,3 +45,26 @@ def test_NSError_p(self): ], ) self.runCmd("process continue") + +@skipIfOutOfTreeDebugserver +def test_runtime_types_efficient_memreads(self): +# Test that we use an efficient reading of memory when reading +

[Lldb-commits] [lldb] [lldb] add a warning if `dirname` is not in the PATH (PR #164494)

2025-10-21 Thread Charles Zablit via lldb-commits
https://github.com/charles-zablit updated https://github.com/llvm/llvm-project/pull/164494 >From 13cdc22b45790ff7a780575df3e17debb2af70e0 Mon Sep 17 00:00:00 2001 From: Charles Zablit Date: Tue, 21 Oct 2025 13:51:59 -0700 Subject: [PATCH 1/3] [lldb] add a warning if `dirname` is not in the PATH

[Lldb-commits] [lldb] [lldb-dap] Send a 'process' event on restart. (PR #163833)

2025-10-21 Thread John Harrison via lldb-commits
https://github.com/ashgti closed https://github.com/llvm/llvm-project/pull/163833 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] 841e1e1 - [lldb-dap] Send a 'process' event on restart. (#163833)

2025-10-21 Thread via lldb-commits
Author: John Harrison Date: 2025-10-21T14:47:12-07:00 New Revision: 841e1e1e17c3bd83e9eaa9e10a057b8217eb8de3 URL: https://github.com/llvm/llvm-project/commit/841e1e1e17c3bd83e9eaa9e10a057b8217eb8de3 DIFF: https://github.com/llvm/llvm-project/commit/841e1e1e17c3bd83e9eaa9e10a057b8217eb8de3.diff

[Lldb-commits] [lldb] [lldb-dap] Fix mutex acquisition order for modules event. (PR #163821)

2025-10-21 Thread John Harrison via lldb-commits
https://github.com/ashgti approved this pull request. LGTM! https://github.com/llvm/llvm-project/pull/163821 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread Peter Rong via lldb-commits
https://github.com/DataCorrupted edited https://github.com/llvm/llvm-project/pull/164471 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [docs][lldb] update the Windows tools instructions (PR #164491)

2025-10-21 Thread David Spickett via lldb-commits
DavidSpickett wrote: @omjavaid just refreshed our Windows on Arm setups, added him to review. https://github.com/llvm/llvm-project/pull/164491 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lld

[Lldb-commits] [lldb] [docs][lldb] update the Windows tools instructions (PR #164491)

2025-10-21 Thread via lldb-commits
@@ -95,36 +95,30 @@ commands below. Windows *** -* Visual Studio 2019. -* The latest Windows SDK. -* The Active Template Library (ATL). -* `GnuWin32 `_ for CoreUtils and Make. -* `Python 3 `_. Ma

[Lldb-commits] [lldb] [docs][lldb] update the Windows tools instructions (PR #164491)

2025-10-21 Thread via lldb-commits
@@ -95,36 +95,30 @@ commands below. Windows *** -* Visual Studio 2019. -* The latest Windows SDK. -* The Active Template Library (ATL). -* `GnuWin32 `_ for CoreUtils and Make. -* `Python 3 `_. Ma

[Lldb-commits] [lldb] [docs][lldb] update the Windows tools instructions (PR #164491)

2025-10-21 Thread via lldb-commits
@@ -95,36 +95,30 @@ commands below. Windows *** -* Visual Studio 2019. -* The latest Windows SDK. -* The Active Template Library (ATL). -* `GnuWin32 `_ for CoreUtils and Make. -* `Python 3 `_. Ma

[Lldb-commits] [lldb] [docs][lldb] update the Windows tools instructions (PR #164491)

2025-10-21 Thread via lldb-commits
https://github.com/Nerixyz commented: Could/should the steps be split into building and testing? Because for building LLDB, only VS, Python, Swig, and DIA are needed (with the last three being technically optional). For the tests, Python and the utils are needed. https://github.com/llvm/llvm-p

[Lldb-commits] [lldb] [docs][lldb] update the Windows tools instructions (PR #164491)

2025-10-21 Thread via lldb-commits
https://github.com/Nerixyz edited https://github.com/llvm/llvm-project/pull/164491 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [docs][lldb] update the Windows tools instructions (PR #164491)

2025-10-21 Thread via lldb-commits
@@ -95,36 +95,30 @@ commands below. Windows *** -* Visual Studio 2019. -* The latest Windows SDK. -* The Active Template Library (ATL). -* `GnuWin32 `_ for CoreUtils and Make. -* `Python 3 `_. Ma

[Lldb-commits] [lldb] [docs][lldb] update the Windows tools instructions (PR #164491)

2025-10-21 Thread via lldb-commits
@@ -95,36 +95,30 @@ commands below. Windows *** -* Visual Studio 2019. -* The latest Windows SDK. -* The Active Template Library (ATL). -* `GnuWin32 `_ for CoreUtils and Make. -* `Python 3 `_. Ma

[Lldb-commits] [lldb] [lldb] Added a warning in case of instruction decode failure (PR #164413)

2025-10-21 Thread David Spickett via lldb-commits
@@ -0,0 +1,4 @@ +int main(int argc, const char *argv[]) { + char my_insns[4] = {0xff, 0xff, 0xff, 0xff}; DavidSpickett wrote: Include the comment from the Python part of the test here as well. https://github.com/llvm/llvm-project/pull/164413 ___

[Lldb-commits] [lldb] [lldb] Added a warning in case of instruction decode failure (PR #164413)

2025-10-21 Thread David Spickett via lldb-commits
@@ -0,0 +1,32 @@ +""" +Test the 'memory read' command when decoding instruction failures. +""" DavidSpickett wrote: Also it means there'll be an upstream bot running this test. https://github.com/llvm/llvm-project/pull/164413

[Lldb-commits] [lldb] [lldb] Added a warning in case of instruction decode failure (PR #164413)

2025-10-21 Thread David Spickett via lldb-commits
@@ -0,0 +1,32 @@ +""" +Test the 'memory read' command when decoding instruction failures. +""" DavidSpickett wrote: I suggest moving this test to a more generic place and only running it on risc-v for the time being. I can add an AArch64 encoding to it. I'd pre

[Lldb-commits] [lldb] [lldb] Added a warning in case of instruction decode failure (PR #164413)

2025-10-21 Thread David Spickett via lldb-commits
@@ -0,0 +1,32 @@ +""" +Test the 'memory read' command when decoding instruction failures. +""" + +import lldb +import lldbsuite.test.lldbutil as lldbutil + +from lldbsuite.test.decorators import * +from lldbsuite.test.lldbtest import * + + +class MemoryReadTestCase(TestBase): +

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread Peter Rong via lldb-commits
@@ -1697,6 +1701,14 @@ void ObjectFileMachO::ProcessSegmentCommand( // isn't stored in the abstracted Sections. m_mach_sections.push_back(sect64); +// Make sure we can load dSYM files whose __DWARF sections exceed the 4GB +// barrier. llvm::MachO::section_64 ha

[Lldb-commits] [lldb] [lldb] add a warning if `dirname` is not in the PATH (PR #164494)

2025-10-21 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Charles Zablit (charles-zablit) Changes This patch adds a check in lldb's API test CMakeLists file to ensure that `dirname` is in the PATH, which is not obvious on Windows. --- Full diff: https://github.com/llvm/llvm-project/pull/164494.di

[Lldb-commits] [lldb] [lldb] add a warning if `dirname` is not in the PATH (PR #164494)

2025-10-21 Thread Charles Zablit via lldb-commits
https://github.com/charles-zablit created https://github.com/llvm/llvm-project/pull/164494 This patch adds a check in lldb's API test CMakeLists file to ensure that `dirname` is in the PATH, which is not obvious on Windows. >From 13cdc22b45790ff7a780575df3e17debb2af70e0 Mon Sep 17 00:00:00 200

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread Ellis Hoag via lldb-commits
@@ -1697,6 +1701,14 @@ void ObjectFileMachO::ProcessSegmentCommand( // isn't stored in the abstracted Sections. m_mach_sections.push_back(sect64); +// Make sure we can load dSYM files whose __DWARF sections exceed the 4GB +// barrier. llvm::MachO::section_64 ha

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread Peter Rong via lldb-commits
@@ -1697,6 +1701,14 @@ void ObjectFileMachO::ProcessSegmentCommand( // isn't stored in the abstracted Sections. m_mach_sections.push_back(sect64); +// Make sure we can load dSYM files whose __DWARF sections exceed the 4GB +// barrier. llvm::MachO::section_64 ha

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread Greg Clayton via lldb-commits
clayborg wrote: > > obj2yaml and yaml2obj are broken for mach-o files and they can't convert a > > yaml file back into a valid mach-o object file > > Is there an issue open for this? Would it be difficult to fix? It can't be fixed, the mach-o file format doesn't support 64 bit section offsets

[Lldb-commits] [clang] [clang-tools-extra] [lldb] [clang] Don't silently inherit the VFS from `FileManager` (PR #164323)

2025-10-21 Thread Qiongsi Wu via lldb-commits
qiongsiwu wrote: I am seeing a trio of methods more or less called together often, but sometimes one is omitted. ``` CompilerInstance::setVirtualFileSystem CompilerInstance::setFileManager CompilerInstance::setSourceManager // This is sometimes omitted. ``` In what cases do we want freedom to s

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread Felipe de Azevedo Piovezan via lldb-commits
https://github.com/felipepiovezan closed https://github.com/llvm/llvm-project/pull/163651 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] f2cb997 - [lldb] Implement Process::ReadMemoryRanges (#163651)

2025-10-21 Thread via lldb-commits
Author: Felipe de Azevedo Piovezan Date: 2025-10-21T12:33:59-07:00 New Revision: f2cb99751882bdd96c683cdeb9e8c5301cbb51cc URL: https://github.com/llvm/llvm-project/commit/f2cb99751882bdd96c683cdeb9e8c5301cbb51cc DIFF: https://github.com/llvm/llvm-project/commit/f2cb99751882bdd96c683cdeb9e8c5301

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread Felipe de Azevedo Piovezan via lldb-commits
felipepiovezan wrote: The AArch bot is still failing with the message below, so I am going to bypass it. > The self-hosted runner lost communication with the server. Verify the machine > is running and has a healthy network connection. Anything in your workflow > that terminates the runner pr

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread Ellis Hoag via lldb-commits
@@ -1697,6 +1701,14 @@ void ObjectFileMachO::ProcessSegmentCommand( // isn't stored in the abstracted Sections. m_mach_sections.push_back(sect64); +// Make sure we can load dSYM files whose __DWARF sections exceed the 4GB +// barrier. llvm::MachO::section_64 ha

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread Ellis Hoag via lldb-commits
ellishg wrote: > obj2yaml and yaml2obj are broken for mach-o files and they can't convert a > yaml file back into a valid mach-o object file Is there an issue open for this? Would it be difficult to fix? https://github.com/llvm/llvm-project/pull/164471 _

[Lldb-commits] [lldb] [lldb][Android] Fix platform process list regression (PR #164333)

2025-10-21 Thread Emre Kultursay via lldb-commits
@@ -652,75 +709,169 @@ PlatformAndroid::FindProcesses(const ProcessInstanceInfoMatch &match_info, return 0; } - // Use 'pidof' command to get PIDs for the process name. - // Quote the process name to handle special characters (spaces, etc.) - std::string pidof_output

[Lldb-commits] [lldb] [lldb][test] When an external stdlib is specified do not link to the system stdlib (PR #164462)

2025-10-21 Thread Michael Buch via lldb-commits
https://github.com/Michael137 edited https://github.com/llvm/llvm-project/pull/164462 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb][Android] Fix platform process list regression (PR #164333)

2025-10-21 Thread Chad Smith via lldb-commits
https://github.com/cs01 edited https://github.com/llvm/llvm-project/pull/164333 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb][Android] Fix platform process list regression (PR #164333)

2025-10-21 Thread Chad Smith via lldb-commits
@@ -652,75 +709,169 @@ PlatformAndroid::FindProcesses(const ProcessInstanceInfoMatch &match_info, return 0; } - // Use 'pidof' command to get PIDs for the process name. - // Quote the process name to handle special characters (spaces, etc.) - std::string pidof_output

[Lldb-commits] [lldb] [lldb] Added a warning in case of instruction decode failure (PR #164413)

2025-10-21 Thread Timur Golubovich via lldb-commits
https://github.com/tgs-sc updated https://github.com/llvm/llvm-project/pull/164413 >From 5b173972d0f85c07283460a4c3e18a5961a3b26c Mon Sep 17 00:00:00 2001 From: Timur Golubovich Date: Fri, 17 Oct 2025 12:12:29 + Subject: [PATCH] [lldb] Added a warning in case of instruction decode failure

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread via lldb-commits
github-actions[bot] wrote: :warning: C/C++ code formatter, clang-format found issues in your code. :warning: You can test this locally with the following command: ``bash git-clang-format --diff origin/main HEAD --extensions cpp -- lldb/source/Plugins/ObjectFile/Mach-O/ObjectFile

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread Greg Clayton via lldb-commits
clayborg wrote: llvm-dsymutil will assert when asserts are enabled when creating large dSYM files that exhibit this bevavior. If asserts are disabled, then llvm-dsymutil can produce such binaries. https://github.com/llvm/llvm-project/pull/164471 ___

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Greg Clayton (clayborg) Changes llvm-dsymutil can produce mach-o files where some sections in __DWARF exceed the 4GB barrier and subsequent sections in the dSYM will be inaccessible because the mach-o section_64 structure only has a 32 bit

[Lldb-commits] [lldb] Enable LLDB to load large dSYM files. (PR #164471)

2025-10-21 Thread Greg Clayton via lldb-commits
https://github.com/clayborg created https://github.com/llvm/llvm-project/pull/164471 llvm-dsymutil can produce mach-o files where some sections in __DWARF exceed the 4GB barrier and subsequent sections in the dSYM will be inaccessible because the mach-o section_64 structure only has a 32 bit f

[Lldb-commits] [lldb] [lldb][test] When an external stdlib is specified do not link to the system stdlib (PR #164462)

2025-10-21 Thread Michael Buch via lldb-commits
https://github.com/Michael137 edited https://github.com/llvm/llvm-project/pull/164462 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb][test] When an external stdlib is specified do not link to the system stdlib (PR #164462)

2025-10-21 Thread Michael Buch via lldb-commits
https://github.com/Michael137 edited https://github.com/llvm/llvm-project/pull/164462 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb][test] When an external stdlib is specified do not link to the system stdlib (PR #164462)

2025-10-21 Thread Michael Buch via lldb-commits
https://github.com/Michael137 edited https://github.com/llvm/llvm-project/pull/164462 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb][test] When an external stdlib is specified do not link to the system stdlib (PR #164462)

2025-10-21 Thread Michael Buch via lldb-commits
https://github.com/Michael137 edited https://github.com/llvm/llvm-project/pull/164462 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb][test] When an external stdlib is specified do not link to the system stdlib (PR #164462)

2025-10-21 Thread Michael Buch via lldb-commits
@@ -386,6 +386,11 @@ ifeq (,$(filter 1, $(USE_LIBSTDCPP) $(USE_LIBCPP) $(USE_SYSTEM_STDLIB))) ifneq "$(LIBCPP_INCLUDE_TARGET_DIR)" "" CXXFLAGS += -cxx-isystem $(LIBCPP_INCLUDE_TARGET_DIR) endif + + # If `-nostdlib++` is not passed, clang will link to the sy

[Lldb-commits] [lldb] [lldb] Added a warning in case of instruction decode failure (PR #164413)

2025-10-21 Thread Jonas Devlieghere via lldb-commits
@@ -157,7 +157,9 @@ static lldb::offset_t DumpInstructions(const DataExtractor &DE, Stream *s, exe_scope->CalculateExecutionContext(exe_ctx); disassembler_sp->GetInstructionList().Dump( s, show_address, show_bytes, show_control_flow_kind, &exe_ctx);

[Lldb-commits] [lldb] [lldb] Added a warning in case of instruction decode failure (PR #164413)

2025-10-21 Thread Jonas Devlieghere via lldb-commits
@@ -157,7 +157,9 @@ static lldb::offset_t DumpInstructions(const DataExtractor &DE, Stream *s, exe_scope->CalculateExecutionContext(exe_ctx); disassembler_sp->GetInstructionList().Dump( s, show_address, show_bytes, show_control_flow_kind, &exe_ctx);

[Lldb-commits] [lldb] [lldb] Fix StdUnorderedMapSynthProvider for GCC (PR #164251)

2025-10-21 Thread David Blaikie via lldb-commits
dwblaikie wrote: Oh, yeah, GCC doesn't produce DW_TAG_template_type_parameter for unnamed template type parameters - yeah, it'd be a valid size optimization for them (relying on the uniqueness/identity of the DW_AT_name, I guess, for any type equivalence checking) - anything that can pull in m

[Lldb-commits] [lldb] [lldb][windows] add a warning if CMake's version is inferior to 3.30 (PR #164346)

2025-10-21 Thread Charles Zablit via lldb-commits
https://github.com/charles-zablit closed https://github.com/llvm/llvm-project/pull/164346 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] d4713ec - [lldb][windows] add a warning if CMake's version is inferior to 3.30 (#164346)

2025-10-21 Thread via lldb-commits
Author: Charles Zablit Date: 2025-10-21T10:53:49-07:00 New Revision: d4713ecb6dbe2d6b1f586508b47ad9391da51d66 URL: https://github.com/llvm/llvm-project/commit/d4713ecb6dbe2d6b1f586508b47ad9391da51d66 DIFF: https://github.com/llvm/llvm-project/commit/d4713ecb6dbe2d6b1f586508b47ad9391da51d66.diff

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread Felipe de Azevedo Piovezan via lldb-commits
felipepiovezan wrote: Added release-mode testing. I found out that gtest has a `ASSERT_DEBUG_DEATH` that just executes statements in release builds (without expecting failures), that's how they recommend doing it (followed by some ifdefs) https://github.com/llvm/llvm-project/pull/163651 __

[Lldb-commits] [lldb] [lldb][test] When an external stdlib is specified do not link to the system stdlib (PR #164462)

2025-10-21 Thread Ebuka Ezike via lldb-commits
https://github.com/da-viper edited https://github.com/llvm/llvm-project/pull/164462 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb][test] When an external stdlib is specified do not link to the system stdlib (PR #164462)

2025-10-21 Thread Ebuka Ezike via lldb-commits
@@ -386,6 +386,11 @@ ifeq (,$(filter 1, $(USE_LIBSTDCPP) $(USE_LIBCPP) $(USE_SYSTEM_STDLIB))) ifneq "$(LIBCPP_INCLUDE_TARGET_DIR)" "" CXXFLAGS += -cxx-isystem $(LIBCPP_INCLUDE_TARGET_DIR) endif + + # If `-nostdlib++` is not passed, clang will link to the sy

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread Felipe de Azevedo Piovezan via lldb-commits
https://github.com/felipepiovezan updated https://github.com/llvm/llvm-project/pull/163651 >From 5b143ddaad4a8369bd31b78b0a5fbf41140f0288 Mon Sep 17 00:00:00 2001 From: Felipe de Azevedo Piovezan Date: Tue, 14 Oct 2025 08:07:51 -0700 Subject: [PATCH 1/9] [lldb] Implement Process::ReadMemoryRang

[Lldb-commits] [lldb] [lldb] Fix StdUnorderedMapSynthProvider for GCC (PR #164251)

2025-10-21 Thread Michael Buch via lldb-commits
https://github.com/Michael137 approved this pull request. https://github.com/llvm/llvm-project/pull/164251 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb] Fix StdUnorderedMapSynthProvider for GCC (PR #164251)

2025-10-21 Thread Michael Buch via lldb-commits
Michael137 wrote: > I am not sure that there is a reliable approach here so it may be better to > have two ways to get data type. The current solution works both for gcc and > clang on my laptop, but it might depend on the compiler version. That's a fair point. But just for testability, I thin

[Lldb-commits] [lldb] [lldb][test] When an external stdlib is specified do not link to the system stdlib (PR #164462)

2025-10-21 Thread Michael Buch via lldb-commits
@@ -386,6 +386,11 @@ ifeq (,$(filter 1, $(USE_LIBSTDCPP) $(USE_LIBCPP) $(USE_SYSTEM_STDLIB))) ifneq "$(LIBCPP_INCLUDE_TARGET_DIR)" "" CXXFLAGS += -cxx-isystem $(LIBCPP_INCLUDE_TARGET_DIR) endif + + # If `-nostdlib++` is not passed, clang will link to the sy

[Lldb-commits] [lldb] [lldb] Fix StdUnorderedMapSynthProvider for GCC (PR #164251)

2025-10-21 Thread Sergei Druzhkov via lldb-commits
DrSergei wrote: I am not sure that there is a reliable approach here so it may be better to have two ways to get data type. The current solution works both for gcc and clang on my laptop, but it might depend on the compiler version. I found an old [review](https://reviews.llvm.org/D14358) whe

[Lldb-commits] [lldb] [lldb][test] When an external stdlib is specified do not link to the system stdlib (PR #164462)

2025-10-21 Thread Ebuka Ezike via lldb-commits
https://github.com/da-viper edited https://github.com/llvm/llvm-project/pull/164462 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb][test] Do not link to the system stdlib (PR #164462)

2025-10-21 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Ebuka Ezike (da-viper) Changes On linux if you specify the an external libc++ and clang will still link to the system's libc++. This patch fixes that. --- Full diff: https://github.com/llvm/llvm-project/pull/164462.diff 1 Files Affected:

[Lldb-commits] [lldb] [lldb][test] Do not link to the system stdlib (PR #164462)

2025-10-21 Thread Ebuka Ezike via lldb-commits
https://github.com/da-viper created https://github.com/llvm/llvm-project/pull/164462 On linux if you specify the an external libc++ and clang will still link to the system's libc++. This patch fixes that. >From 2da770c87999871d160d6c86d4e2b3de9b79c536 Mon Sep 17 00:00:00 2001 From: Ebuka Ezike

[Lldb-commits] [lldb] [lldb] Fix StdUnorderedMapSynthProvider for GCC (PR #164251)

2025-10-21 Thread Sergei Druzhkov via lldb-commits
https://github.com/DrSergei updated https://github.com/llvm/llvm-project/pull/164251 >From efe6fbd8c3aae0889bda2ec403a6baa64cae13f5 Mon Sep 17 00:00:00 2001 From: Druzhkov Sergei Date: Mon, 20 Oct 2025 15:45:30 +0300 Subject: [PATCH] [lldb] Fix StdUnorderedMapSynthProvider for GCC --- lldb/ex

[Lldb-commits] [lldb] [llvm] [lldb][DeclVendor] Remove ClangDeclVendor (PR #164380)

2025-10-21 Thread Alex Langford via lldb-commits
bulbazord wrote: Thanks! https://github.com/llvm/llvm-project/pull/164380 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [llvm] [lldb][DeclVendor] Remove ClangDeclVendor (PR #164380)

2025-10-21 Thread Michael Buch via lldb-commits
https://github.com/Michael137 closed https://github.com/llvm/llvm-project/pull/164380 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] cc77d76 - [lldb][DeclVendor] Remove ClangDeclVendor (#164380)

2025-10-21 Thread via lldb-commits
Author: Michael Buch Date: 2025-10-21T18:00:46+01:00 New Revision: cc77d76a9e5069855e82cec5b6ddb93e8b7bcca9 URL: https://github.com/llvm/llvm-project/commit/cc77d76a9e5069855e82cec5b6ddb93e8b7bcca9 DIFF: https://github.com/llvm/llvm-project/commit/cc77d76a9e5069855e82cec5b6ddb93e8b7bcca9.diff

[Lldb-commits] [lldb] [lldb][ObjC][NFC] Use early-return in AppleObjCDeclVendor::FindDecls (PR #164371)

2025-10-21 Thread Michael Buch via lldb-commits
https://github.com/Michael137 closed https://github.com/llvm/llvm-project/pull/164371 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] e45b72d - [lldb][ObjC][NFC] Use early-return in AppleObjCDeclVendor::FindDecls (#164371)

2025-10-21 Thread via lldb-commits
Author: Michael Buch Date: 2025-10-21T18:00:34+01:00 New Revision: e45b72da82a3ace02db19bccedbec7e4f94191c5 URL: https://github.com/llvm/llvm-project/commit/e45b72da82a3ace02db19bccedbec7e4f94191c5 DIFF: https://github.com/llvm/llvm-project/commit/e45b72da82a3ace02db19bccedbec7e4f94191c5.diff

[Lldb-commits] [lldb] [llvm] [lldb-dap] Add multi-session support with shared debugger instances (PR #163653)

2025-10-21 Thread Walter Erquinigo via lldb-commits
@@ -0,0 +1,125 @@ +//===-- DAPSessionManager.h *- C++ -*-===// +// +// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions. +// See https://llvm.org/LICENSE.txt for license information. +// SPDX-License-Identifier: Apac

[Lldb-commits] [lldb] [llvm] [lldb-dap] Add multi-session support with shared debugger instances (PR #163653)

2025-10-21 Thread Walter Erquinigo via lldb-commits
@@ -0,0 +1,125 @@ +//===-- DAPSessionManager.h *- C++ -*-===// +// +// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions. +// See https://llvm.org/LICENSE.txt for license information. +// SPDX-License-Identifier: Apac

[Lldb-commits] [lldb] [lldb][Android] Fix platform process list regression (PR #164333)

2025-10-21 Thread via lldb-commits
@@ -652,75 +709,169 @@ PlatformAndroid::FindProcesses(const ProcessInstanceInfoMatch &match_info, return 0; } - // Use 'pidof' command to get PIDs for the process name. - // Quote the process name to handle special characters (spaces, etc.) - std::string pidof_output

[Lldb-commits] [lldb] [lldb][ObjC][NFC] Use early-return in AppleObjCDeclVendor::FindDecls (PR #164371)

2025-10-21 Thread Adrian Prantl via lldb-commits
https://github.com/adrian-prantl approved this pull request. https://github.com/llvm/llvm-project/pull/164371 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [llvm] [lldb][DeclVendor] Remove ClangDeclVendor (PR #164380)

2025-10-21 Thread Adrian Prantl via lldb-commits
https://github.com/adrian-prantl approved this pull request. https://github.com/llvm/llvm-project/pull/164380 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [NFCI][lldb] Omit redundant member initializer list (PR #164451)

2025-10-21 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Raul Tambre (tambry) Changes These all have member initializers of the same value so they're redundant. Fixes: 47b9aadb3215e914119d0c45827ea58cb7499204 --- Full diff: https://github.com/llvm/llvm-project/pull/164451.diff 1 Files Affected

[Lldb-commits] [lldb] [NFCI][lldb] Omit redundant member initializer list (PR #164451)

2025-10-21 Thread Raul Tambre via lldb-commits
https://github.com/tambry created https://github.com/llvm/llvm-project/pull/164451 These all have member initializers of the same value so they're redundant. Fixes: 47b9aadb3215e914119d0c45827ea58cb7499204 >From 39771d28f98a7fb43cd5b25ce6c5867af6722aea Mon Sep 17 00:00:00 2001 From: Raul Tambr

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread David Spickett via lldb-commits
https://github.com/DavidSpickett approved this pull request. I would like to see the non-assert side of the ASSERT_DEATH paths tested (in non-asserts builds, not in the same build of course). Otherwise LGTM so in the interests of time I'm approving and I'm sure you'll figure it out. https://g

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread David Spickett via lldb-commits
@@ -225,3 +226,129 @@ TEST_F(MemoryTest, TesetMemoryCacheRead) { // instead of using an // old cache } + +/// A process class that, when asked to read memory from some

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread David Spickett via lldb-commits
@@ -225,3 +226,129 @@ TEST_F(MemoryTest, TesetMemoryCacheRead) { // instead of using an // old cache } + +/// A process class that, when asked to read memory from some

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread Felipe de Azevedo Piovezan via lldb-commits
https://github.com/felipepiovezan updated https://github.com/llvm/llvm-project/pull/163651 >From 5b143ddaad4a8369bd31b78b0a5fbf41140f0288 Mon Sep 17 00:00:00 2001 From: Felipe de Azevedo Piovezan Date: Tue, 14 Oct 2025 08:07:51 -0700 Subject: [PATCH 1/8] [lldb] Implement Process::ReadMemoryRang

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread Felipe de Azevedo Piovezan via lldb-commits
felipepiovezan wrote: Added death tests, removed references to "chunks" in the comments, rewrote `return llvm::SmallVector>(ranges.size());` into something more palatable https://github.com/llvm/llvm-project/pull/163651 ___ lldb-commits mailing list

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread Felipe de Azevedo Piovezan via lldb-commits
https://github.com/felipepiovezan updated https://github.com/llvm/llvm-project/pull/163651 >From 5b143ddaad4a8369bd31b78b0a5fbf41140f0288 Mon Sep 17 00:00:00 2001 From: Felipe de Azevedo Piovezan Date: Tue, 14 Oct 2025 08:07:51 -0700 Subject: [PATCH 1/7] [lldb] Implement Process::ReadMemoryRang

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread Felipe de Azevedo Piovezan via lldb-commits
https://github.com/felipepiovezan updated https://github.com/llvm/llvm-project/pull/163651 >From 5b143ddaad4a8369bd31b78b0a5fbf41140f0288 Mon Sep 17 00:00:00 2001 From: Felipe de Azevedo Piovezan Date: Tue, 14 Oct 2025 08:07:51 -0700 Subject: [PATCH 1/6] [lldb] Implement Process::ReadMemoryRang

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread Felipe de Azevedo Piovezan via lldb-commits
https://github.com/felipepiovezan updated https://github.com/llvm/llvm-project/pull/163651 >From 5b143ddaad4a8369bd31b78b0a5fbf41140f0288 Mon Sep 17 00:00:00 2001 From: Felipe de Azevedo Piovezan Date: Tue, 14 Oct 2025 08:07:51 -0700 Subject: [PATCH 1/6] [lldb] Implement Process::ReadMemoryRang

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread David Spickett via lldb-commits
@@ -225,3 +226,62 @@ TEST_F(MemoryTest, TesetMemoryCacheRead) { // instead of using an // old cache } + +/// A process class that, when asked to read memory from some a

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread David Spickett via lldb-commits
@@ -1971,6 +1971,45 @@ size_t Process::ReadMemory(addr_t addr, void *buf, size_t size, Status &error) { } } +llvm::SmallVector> +Process::ReadMemoryRanges(llvm::ArrayRef> ranges, + llvm::MutableArrayRef buffer) { + auto total_ranges_len = llvm::sum

[Lldb-commits] [lldb] [lldb] Implement Process::ReadMemoryRanges (PR #163651)

2025-10-21 Thread David Spickett via lldb-commits
@@ -1971,6 +1971,45 @@ size_t Process::ReadMemory(addr_t addr, void *buf, size_t size, Status &error) { } } +llvm::SmallVector> +Process::ReadMemoryRanges(llvm::ArrayRef> ranges, + llvm::MutableArrayRef buffer) { + auto total_ranges_len = llvm::sum

[Lldb-commits] [clang] [lldb] [lldb] Re-use clang's keyword enable/disable mechanism in CPlusPlusNameParser.cpp (PR #164284)

2025-10-21 Thread Michael Buch via lldb-commits
@@ -46,6 +46,59 @@ class LangOptions; class MultiKeywordSelector; class SourceLocation; +// This is an inline namespace to allow both clang and lldb to use them without +// namespace prefixes (via `using namespace` in lldb's case). +inline namespace TokenKeyEnumerators { -

[Lldb-commits] [lldb] [lldb] Added a warning in case of instruction decode failure (PR #164413)

2025-10-21 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-backend-risc-v Author: Timur Golubovich (tgs-sc) Changes While testing baremetal lldb, I came across a situation that if an instruction could not be disassembled, lldb will print nothing as an output which might be a bit strange. I added at least print

[Lldb-commits] [lldb] [lldb] Added a warning in case of instruction decode failure (PR #164413)

2025-10-21 Thread Timur Golubovich via lldb-commits
tgs-sc wrote: @Michael137, @JDevlieghere, Hi! Can you please look at this patch? https://github.com/llvm/llvm-project/pull/164413 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb] Added a warning in case of instruction decode failure (PR #164413)

2025-10-21 Thread Timur Golubovich via lldb-commits
https://github.com/tgs-sc created https://github.com/llvm/llvm-project/pull/164413 While testing baremetal lldb, I came across a situation that if an instruction could not be disassembled, lldb will print nothing as an output which might be a bit strange. I added at least printing warning in t

[Lldb-commits] [lldb] [LLDB][NativePDB] Require `target-windows` for `func-symbols.test` (PR #164406)

2025-10-21 Thread via lldb-commits
https://github.com/Nerixyz closed https://github.com/llvm/llvm-project/pull/164406 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] d9556d3 - [LLDB][NativePDB] Require `target-windows` for `func-symbols.test` (#164406)

2025-10-21 Thread via lldb-commits
Author: nerix Date: 2025-10-21T12:23:50Z New Revision: d9556d3475510d6d0910ecd6e5e07779302c90ef URL: https://github.com/llvm/llvm-project/commit/d9556d3475510d6d0910ecd6e5e07779302c90ef DIFF: https://github.com/llvm/llvm-project/commit/d9556d3475510d6d0910ecd6e5e07779302c90ef.diff LOG: [LLDB][

[Lldb-commits] [lldb] [LLDB][NativePDB] Require `target-windows` for `func-symbols.test` (PR #164406)

2025-10-21 Thread via lldb-commits
https://github.com/Nerixyz auto_merge_enabled https://github.com/llvm/llvm-project/pull/164406 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [LLDB][PDB] Split `func-symbols.test` between DIA and native (PR #163733)

2025-10-21 Thread LLVM Continuous Integration via lldb-commits
llvm-ci wrote: LLVM Buildbot has detected a new failure on builder `lldb-remote-linux-win` running on `as-builder-10` while building `lldb` at step 18 "test-check-lldb-shell". Full details are available at: https://lab.llvm.org/buildbot/#/builders/197/builds/10070 Here is the relevant piece

[Lldb-commits] [lldb] [LLDB][NativePDB] Require `target-windows` for `func-symbols.test` (PR #164406)

2025-10-21 Thread via lldb-commits
https://github.com/Nerixyz edited https://github.com/llvm/llvm-project/pull/164406 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [LLDB][NativePDB] Require `target-windows` for `func-symbols.test` (PR #164406)

2025-10-21 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: nerix (Nerixyz) Changes The test builds files for Windows, so the target has to be required. Fixes the failure from https://github.com/llvm/llvm-project/pull/163733#issuecomment-3426275296. --- Full diff: https://github.com/llvm/llvm-proj

[Lldb-commits] [lldb] [LLDB][NativePDB] Require `target-windows` for `func-symbols.test` (PR #164406)

2025-10-21 Thread via lldb-commits
https://github.com/Nerixyz created https://github.com/llvm/llvm-project/pull/164406 The test builds files for Windows, so the target has to be required. Fixes the failure from https://github.com/llvm/llvm-project/pull/163733#issuecomment-3426275296. >From 3def757bf06c2939e9cb0ab335e6889fb7efe

[Lldb-commits] [lldb] [LLDB][PDB] Split `func-symbols.test` between DIA and native (PR #163733)

2025-10-21 Thread LLVM Continuous Integration via lldb-commits
llvm-ci wrote: LLVM Buildbot has detected a new failure on builder `lldb-remote-linux-ubuntu` running on `as-builder-9` while building `lldb` at step 17 "test-check-lldb-shell". Full details are available at: https://lab.llvm.org/buildbot/#/builders/195/builds/16275 Here is the relevant pie

[Lldb-commits] [lldb] [LLDB][PDB] Run `pointers.test` with both plugins (PR #163623)

2025-10-21 Thread via lldb-commits
https://github.com/Nerixyz closed https://github.com/llvm/llvm-project/pull/163623 ___ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

  1   2   >