[Lldb-commits] [lldb] [llvm] [CI] monolithic-linux improvements (PR #135499)

2025-04-13 Thread Matheus Izvekov via lldb-commits
https://github.com/mizvekov updated https://github.com/llvm/llvm-project/pull/135499 >From 456d2fd5f7341eaee6278231b8024b4608d7dc53 Mon Sep 17 00:00:00 2001 From: Matheus Izvekov Date: Sat, 12 Apr 2025 12:57:08 -0300 Subject: [PATCH] [CI] monolithic-linux improvements Some improvements to mono

[Lldb-commits] [lldb] [lldb][Language] Change GetFunctionDisplayName to take SymbolContext by reference (PR #135536)

2025-04-13 Thread Michael Buch via lldb-commits
https://github.com/Michael137 updated https://github.com/llvm/llvm-project/pull/135536 >From e156553442b071e842e97bbad0ad89d03d2183ca Mon Sep 17 00:00:00 2001 From: Michael Buch Date: Sun, 13 Apr 2025 11:08:09 +0100 Subject: [PATCH 1/2] [lldb][Language] Change GetFunctionDisplayName to take Sy

[Lldb-commits] [lldb] 52e45a7 - [lldb][Language] Change GetFunctionDisplayName to take SymbolContext by reference (#135536)

2025-04-13 Thread via lldb-commits
Author: Michael Buch Date: 2025-04-13T23:19:26+01:00 New Revision: 52e45a79ad24f8a2347a5566e6abaa207918df62 URL: https://github.com/llvm/llvm-project/commit/52e45a79ad24f8a2347a5566e6abaa207918df62 DIFF: https://github.com/llvm/llvm-project/commit/52e45a79ad24f8a2347a5566e6abaa207918df62.diff

[Lldb-commits] [lldb] 1e153b7 - [lldb][Format] Display only the inlined frame name in backtraces if available (#135343)

2025-04-13 Thread via lldb-commits
Author: Michael Buch Date: 2025-04-13T23:21:52+01:00 New Revision: 1e153b782ea3054c02dd0016314fca11a5d781da URL: https://github.com/llvm/llvm-project/commit/1e153b782ea3054c02dd0016314fca11a5d781da DIFF: https://github.com/llvm/llvm-project/commit/1e153b782ea3054c02dd0016314fca11a5d781da.diff

[Lldb-commits] [lldb] a3f8359 - [lldb][test] Fix NativePDB/inline_sites_live.cpp inlined frame format

2025-04-13 Thread Michael Buch via lldb-commits
Author: Michael Buch Date: 2025-04-14T06:31:50+01:00 New Revision: a3f8359410eb7e14c4a52b47f36e433af40c05e9 URL: https://github.com/llvm/llvm-project/commit/a3f8359410eb7e14c4a52b47f36e433af40c05e9 DIFF: https://github.com/llvm/llvm-project/commit/a3f8359410eb7e14c4a52b47f36e433af40c05e9.diff

[Lldb-commits] [lldb] [lldb] Remove ProcessRunLock::TrySetRunning (PR #135455)

2025-04-13 Thread Pavel Labath via lldb-commits
https://github.com/labath approved this pull request. I was looking at this code as well, and I've (also) came to the conclusion that `TrySetRunning` is a problem. https://github.com/llvm/llvm-project/pull/135455 ___ lldb-commits mailing list lldb-com

[Lldb-commits] [lldb] [lldb] Remove ProcessRunLock::TrySetRunning (PR #135455)

2025-04-13 Thread Pavel Labath via lldb-commits
@@ -29,8 +29,13 @@ class ProcessRunLock { bool ReadTryLock(); bool ReadUnlock(); + + /// Set the process to running. Returns true if the process was stopped. + /// Return false if the process was running. bool SetRunning(); - bool TrySetRunning(); + + /// Set the pr

[Lldb-commits] [lldb] [lldb][Format] Display only the inlined frame name in backtraces if available (PR #135343)

2025-04-13 Thread Michael Buch via lldb-commits
https://github.com/Michael137 closed https://github.com/llvm/llvm-project/pull/135343 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb] Remove ProcessRunLock::TrySetRunning (PR #135455)

2025-04-13 Thread Pavel Labath via lldb-commits
https://github.com/labath edited https://github.com/llvm/llvm-project/pull/135455 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb] Remove ProcessRunLock::TrySetRunning (PR #135455)

2025-04-13 Thread Pavel Labath via lldb-commits
@@ -60,6 +49,7 @@ bool ProcessRunLock::SetStopped() { ::pthread_rwlock_unlock(&m_rwlock); labath wrote: This should also do the `was_running` dance. https://github.com/llvm/llvm-project/pull/135455 ___ lldb-commits

[Lldb-commits] [lldb] [lldb] returning command completions up to a maximum (PR #135565)

2025-04-13 Thread Ely Ronnen via lldb-commits
https://github.com/eronnen created https://github.com/llvm/llvm-project/pull/135565 - Adding `max_return_elements` field to `CompletionRequest`. - adding maximum checks to `SymbolCompleter` and `SourceFileCompleter`. Fixes #135553 >From 1b45ab684446f2ff67c8ab89d00422ffcf2f7734 Mon Sep 17 00:00

[Lldb-commits] [lldb] 99df442 - Skip test on Darwin

2025-04-13 Thread Adrian Prantl via lldb-commits
Author: Adrian Prantl Date: 2025-04-13T14:40:41-07:00 New Revision: 99df442df1f88c1078c433618c75ee62f3dd8512 URL: https://github.com/llvm/llvm-project/commit/99df442df1f88c1078c433618c75ee62f3dd8512 DIFF: https://github.com/llvm/llvm-project/commit/99df442df1f88c1078c433618c75ee62f3dd8512.diff

[Lldb-commits] [lldb] [lldb] returning command completions up to a maximum (PR #135565)

2025-04-13 Thread via lldb-commits
github-actions[bot] wrote: Thank you for submitting a Pull Request (PR) to the LLVM Project! This PR will be automatically labeled and the relevant teams will be notified. If you wish to, you can add reviewers by using the "Reviewers" section on this page. If this is not working for you, it

[Lldb-commits] [lldb] [lldb][Language] Change GetFunctionDisplayName to take SymbolContext by reference (PR #135536)

2025-04-13 Thread Adrian Prantl via lldb-commits
https://github.com/adrian-prantl approved this pull request. https://github.com/llvm/llvm-project/pull/135536 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb][Format] Display only the inlined frame name in backtraces if available (PR #135343)

2025-04-13 Thread Adrian Prantl via lldb-commits
https://github.com/adrian-prantl approved this pull request. https://github.com/llvm/llvm-project/pull/135343 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb] returning command completions up to a maximum (PR #135565)

2025-04-13 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Ely Ronnen (eronnen) Changes - Adding `max_return_elements` field to `CompletionRequest`. - adding maximum checks to `SymbolCompleter` and `SourceFileCompleter`. Fixes #135553 --- Full diff: https://github.com/llvm/llvm-project/pull/135565

[Lldb-commits] [lldb] [lldb] returning command completions up to a maximum (PR #135565)

2025-04-13 Thread Ely Ronnen via lldb-commits
https://github.com/eronnen updated https://github.com/llvm/llvm-project/pull/135565 >From 66333e243f22ca68e85dea1fe3c26b02203df975 Mon Sep 17 00:00:00 2001 From: Ely Ronnen Date: Sun, 13 Apr 2025 20:46:56 +0200 Subject: [PATCH] [lldb] returning command completions up to a maximum - Adding `max

[Lldb-commits] [lldb] [lldb][AArch64] Fix Apple M4 on Linux (PR #135563)

2025-04-13 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Marcel Laverdet (laverdet) Changes This architecture implements SSVE but does not implement SVE. More information is included in #121693 cc: @DavidSpickett --- Full diff: https://github.com/llvm/llvm-project/pull/135563.diff 1 Files Aff

[Lldb-commits] [lldb] [lldb][AArch64] Fix Apple M4 on Linux (PR #135563)

2025-04-13 Thread Marcel Laverdet via lldb-commits
https://github.com/laverdet created https://github.com/llvm/llvm-project/pull/135563 This architecture implements SSVE but does not implement SVE. More information is included in #121693 cc: @DavidSpickett >From 5c85083f41230ec83bd862ebf2723d03d9bcfb65 Mon Sep 17 00:00:00 2001 From: Marcel La

[Lldb-commits] [lldb] [lldb][AArch64] Fix Apple M4 on Linux (PR #135563)

2025-04-13 Thread via lldb-commits
github-actions[bot] wrote: Thank you for submitting a Pull Request (PR) to the LLVM Project! This PR will be automatically labeled and the relevant teams will be notified. If you wish to, you can add reviewers by using the "Reviewers" section on this page. If this is not working for you, it

[Lldb-commits] [lldb] [lldb] Remove ProcessRunLock::TrySetRunning (PR #135455)

2025-04-13 Thread Pavel Labath via lldb-commits
labath wrote: Thanks for looking into this. https://github.com/llvm/llvm-project/pull/135455 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[Lldb-commits] [lldb] [lldb/cmake] Normalize use of HAVE_LIBCOMPRESSION (PR #135528)

2025-04-13 Thread Pavel Labath via lldb-commits
https://github.com/labath created https://github.com/llvm/llvm-project/pull/135528 I *think* this was the reason behind the failures in 2fd860c1f559c0b0be66cc000e38270a04d0a1a3: the clang include tool showed the Config.h headers as unused, and because the macro was referenced through an `#ifd

[Lldb-commits] [lldb] [lldb/cmake] Normalize use of HAVE_LIBCOMPRESSION (PR #135528)

2025-04-13 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Pavel Labath (labath) Changes I *think* this was the reason behind the failures in 2fd860c1f559c0b0be66cc000e38270a04d0a1a3: the clang include tool showed the Config.h headers as unused, and because the macro was referenced through an `#i

[Lldb-commits] [lldb] 1c5ce2d - Reapply "[lldb] ProcessGdbRemote header gardning"

2025-04-13 Thread Pavel Labath via lldb-commits
Author: Pavel Labath Date: 2025-04-13T09:52:30+02:00 New Revision: 1c5ce2d74fa3ee15d1cb2e092cce0754c8ce19fa URL: https://github.com/llvm/llvm-project/commit/1c5ce2d74fa3ee15d1cb2e092cce0754c8ce19fa DIFF: https://github.com/llvm/llvm-project/commit/1c5ce2d74fa3ee15d1cb2e092cce0754c8ce19fa.diff

[Lldb-commits] [lldb] [lldb][Language] Change GetFunctionDisplayName to take SymbolContext by reference (PR #135536)

2025-04-13 Thread Michael Buch via lldb-commits
https://github.com/Michael137 created https://github.com/llvm/llvm-project/pull/135536 Both the `CPlusPlusLanguage` plugins and the Swift language plugin already assume the `sc != nullptr`. And all `FormatEntity` callsites of `GetFunctionDisplayName` already check for nullptr before passing `s

[Lldb-commits] [lldb] [lldb][Language] Change GetFunctionDisplayName to take SymbolContext by reference (PR #135536)

2025-04-13 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Michael Buch (Michael137) Changes Both the `CPlusPlusLanguage` plugins and the Swift language plugin already assume the `sc != nullptr`. And all `FormatEntity` callsites of `GetFunctionDisplayName` already check for nullptr before passing

[Lldb-commits] [lldb] [lldb][Language] Change GetFunctionDisplayName to take SymbolContext by reference (PR #135536)

2025-04-13 Thread Michael Buch via lldb-commits
https://github.com/Michael137 updated https://github.com/llvm/llvm-project/pull/135536 >From e156553442b071e842e97bbad0ad89d03d2183ca Mon Sep 17 00:00:00 2001 From: Michael Buch Date: Sun, 13 Apr 2025 11:08:09 +0100 Subject: [PATCH] [lldb][Language] Change GetFunctionDisplayName to take Symbol

[Lldb-commits] [lldb] [lldb][lldb-dap] explicitly set the expr as an alias for expression. (PR #134562)

2025-04-13 Thread Ebuka Ezike via lldb-commits
https://github.com/da-viper updated https://github.com/llvm/llvm-project/pull/134562 >From be69e129667cac2ab75597bb3ed02f7d6da39bce Mon Sep 17 00:00:00 2001 From: Ebuka Ezike Date: Sun, 6 Apr 2025 01:36:12 +0100 Subject: [PATCH 1/3] [lldb][lldb-dap] explicitly set the expr as an alias for expr

[Lldb-commits] [lldb] [lldb][lldb-dap] explicitly set the expr as an alias for expression. (PR #134562)

2025-04-13 Thread Ebuka Ezike via lldb-commits
da-viper wrote: > So we need a better solution to this DAP problem than just adding aliases. How about for aliases that are mentioned in the documentation, we explicitly set those as aliases. https://github.com/llvm/llvm-project/pull/134562 ___ lldb-

[Lldb-commits] [lldb] [llvm] [CI] monolithic-linux improvements (PR #135499)

2025-04-13 Thread Matheus Izvekov via lldb-commits
https://github.com/mizvekov updated https://github.com/llvm/llvm-project/pull/135499 >From 70021811ab6551ed38d04a2f740b9e6b330e3290 Mon Sep 17 00:00:00 2001 From: Matheus Izvekov Date: Sat, 12 Apr 2025 12:57:08 -0300 Subject: [PATCH] [CI] monolithic-linux improvements Some improvements to mono

[Lldb-commits] [lldb] [llvm] [CI] monolithic-linux improvements (PR #135499)

2025-04-13 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Matheus Izvekov (mizvekov) Changes Some improvements to monolithic-linux CI: 1) Add correct configuration and dependencies for LLDB testing which is actually relevant for clang changes. 2) Skip clang installation and separate configurati

[Lldb-commits] [lldb] [llvm] [CI] monolithic-linux improvements (PR #135499)

2025-04-13 Thread Matheus Izvekov via lldb-commits
@@ -130,12 +132,11 @@ def _add_dependencies(projects: Set[str]) -> Set[str]: def _compute_projects_to_test(modified_projects: Set[str], platform: str) -> Set[str]: projects_to_test = set() for modified_project in modified_projects: -# Skip all projects where we

[Lldb-commits] [lldb] [lldb-dap] fix inconsistent debugAdapterHostname argument name (PR #135544)

2025-04-13 Thread Ely Ronnen via lldb-commits
https://github.com/eronnen created https://github.com/llvm/llvm-project/pull/135544 the argument is written as `debugAdapterHostname` in package.json but used as `debugAdapterHost` >From 2428391183090dd68a5433b8c3a89bf8ad326625 Mon Sep 17 00:00:00 2001 From: Ely Ronnen Date: Sun, 13 Apr 2025

[Lldb-commits] [lldb] [lldb-dap] fix inconsistent debugAdapterHostname argument name (PR #135544)

2025-04-13 Thread via lldb-commits
llvmbot wrote: @llvm/pr-subscribers-lldb Author: Ely Ronnen (eronnen) Changes the argument is written as `debugAdapterHostname` in package.json but used as `debugAdapterHost` --- Full diff: https://github.com/llvm/llvm-project/pull/135544.diff 2 Files Affected: - (modified) lldb/tools

[Lldb-commits] [lldb] [lldb-dap] fix inconsistent debugAdapterHostname argument name (PR #135544)

2025-04-13 Thread via lldb-commits
github-actions[bot] wrote: Thank you for submitting a Pull Request (PR) to the LLVM Project! This PR will be automatically labeled and the relevant teams will be notified. If you wish to, you can add reviewers by using the "Reviewers" section on this page. If this is not working for you, it