https://github.com/jeffreytan81 updated
https://github.com/llvm/llvm-project/pull/108907
>From 6e84ab9a14e63c58e1facdbf9a695c093882b37b Mon Sep 17 00:00:00 2001
From: jeffreytan81
Date: Mon, 19 Aug 2024 10:57:35 -0700
Subject: [PATCH 1/2] Fix StartDebuggingRequestHandler/ReplModeRequestHandler
https://github.com/jeffreytan81 updated
https://github.com/llvm/llvm-project/pull/108907
>From 6e84ab9a14e63c58e1facdbf9a695c093882b37b Mon Sep 17 00:00:00 2001
From: jeffreytan81
Date: Mon, 19 Aug 2024 10:57:35 -0700
Subject: [PATCH 1/2] Fix StartDebuggingRequestHandler/ReplModeRequestHandler
@@ -301,7 +301,8 @@ using Entry = llvm::DWARFDebugNames::Entry;
/// If any parent does not have an `IDX_parent`, or the Entry data is
corrupted,
/// nullopt is returned.
std::optional>
-getParentChain(Entry entry, uint32_t max_parents) {
+getParentChain(Entry entry,
+
@@ -3306,6 +3306,8 @@ bool CommandInterpreter::SaveTranscript(
result.SetStatus(eReturnStatusSuccessFinishNoResult);
result.AppendMessageWithFormat("Session's transcripts saved to %s\n",
output_file->c_str());
+ if (!GetSaveTranscript())
+
Author: Jason Molenda
Date: 2024-09-25T21:36:51-07:00
New Revision: 3d0469516c687b6dad3e6482fd94d64c65fa4a01
URL:
https://github.com/llvm/llvm-project/commit/3d0469516c687b6dad3e6482fd94d64c65fa4a01
DIFF:
https://github.com/llvm/llvm-project/commit/3d0469516c687b6dad3e6482fd94d64c65fa4a01.diff
Author: Jason Molenda
Date: 2024-09-25T21:51:38-07:00
New Revision: 0f984976897857a8f4003063be6fa38a733fa624
URL:
https://github.com/llvm/llvm-project/commit/0f984976897857a8f4003063be6fa38a733fa624
DIFF:
https://github.com/llvm/llvm-project/commit/0f984976897857a8f4003063be6fa38a733fa624.diff
JDevlieghere wrote:
Change makes sense, but is there a way to test this?
https://github.com/llvm/llvm-project/pull/110066
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/jeffreytan81 created
https://github.com/llvm/llvm-project/pull/110062
## Summary
This PR is a continuation of https://github.com/llvm/llvm-project/pull/108907
by using `.debug_names` parent chain faster lookup for namespaces.
## Implementation
Similar to https://github.com/
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: None (jeffreytan81)
Changes
## Summary
This PR is a continuation of https://github.com/llvm/llvm-project/pull/108907
by using `.debug_names` parent chain faster lookup for namespaces.
## Implementation
Similar to https://github.com/llvm/l
https://github.com/jeffreytan81 ready_for_review
https://github.com/llvm/llvm-project/pull/110062
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
jeffreytan81 wrote:
This is a stack PR from https://github.com/llvm/llvm-project/pull/108907, so
please review the new namespaces lookup changes and ignore the changes in
https://github.com/llvm/llvm-project/pull/108907. Let me know if there is a way
to only show the delta changes (not merged
https://github.com/adrian-prantl updated
https://github.com/llvm/llvm-project/pull/106470
>From 9f4ba3fdb8b144736e51134ced3019a2c57ca861 Mon Sep 17 00:00:00 2001
From: Adrian Prantl
Date: Wed, 28 Aug 2024 10:04:33 -0700
Subject: [PATCH 1/2] [lldb] Store expression evaluator diagnostics in an
l
https://github.com/Jlalond created
https://github.com/llvm/llvm-project/pull/110065
This fixes a functionality gap with GDB, where GDB will properly decode the
stop reason and give the address for SIGSEGV. I also added descriptions to all
stop reasons, following the same code path that the Nat
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jacob Lalonde (Jlalond)
Changes
This fixes a functionality gap with GDB, where GDB will properly decode the
stop reason and give the address for SIGSEGV. I also added descriptions to all
stop reasons, following the same code path that the
adrian-prantl wrote:
> > > This seems like it could be problematic for IDEs, if they don't print the
> > > error in the same window as the expression being evaluated. The arrows
> > > could end up pointing to nowhere, or to the wrong place in the expression
> > > (if we don't get the right off
https://github.com/GeorgeHuyubo created
https://github.com/llvm/llvm-project/pull/110066
The gnu build id was lost while creating the new module spec, this result in
the SymbolLocatorDebuginfod not able to locate symbol file.
before this change while connecting to debuginfod server I am seeing
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: None (GeorgeHuyubo)
Changes
The gnu build id was lost while creating the new module spec, this result in
the SymbolLocatorDebuginfod not able to locate symbol file.
before this change while connecting to debuginfod server I am seeing this
@@ -254,14 +256,46 @@ class ClangDiagnosticManagerAdapter : public
clang::DiagnosticConsumer {
std::string stripped_output =
std::string(llvm::StringRef(m_output).trim());
- auto new_diagnostic = std::make_unique(
- stripped_output, severity, Inf
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 df4f828938db807fc7c4611896fe9659af482e81
8e1c59729905fb89a8764ace3dfa0d04119d273e --e
https://github.com/ZequanWu created
https://github.com/llvm/llvm-project/pull/110058
They are close enough to swap lldb's `DWARFDebugArangeSet` with the llvm one.
The difference is that llvm's `DWARFDebugArangeSet` add empty ranges when
extracting. To accommodate this, `DWARFDebugAranges` in l
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Zequan Wu (ZequanWu)
Changes
They are close enough to swap lldb's `DWARFDebugArangeSet` with the llvm one.
The difference is that llvm's `DWARFDebugArangeSet` add empty ranges when
extracting. To accommodate this, `DWARFDebugAranges` in ll
https://github.com/adrian-prantl updated
https://github.com/llvm/llvm-project/pull/106442
>From d6eec42d53f17bfa34fec7623d1616fbca0a0140 Mon Sep 17 00:00:00 2001
From: Adrian Prantl
Date: Wed, 28 Aug 2024 10:04:33 -0700
Subject: [PATCH] [lldb] Store expression evaluator diagnostics in an
llvm:
@@ -61,8 +65,50 @@ std::string DiagnosticManager::GetString(char separator) {
stream << message.drop_front(severity_pos + severity.size());
stream << separator;
}
+ return str;
+}
- return ret;
+void DiagnosticManager::Dump(Log *log) {
+ if (!log)
+return;
https://github.com/ZequanWu updated
https://github.com/llvm/llvm-project/pull/110058
>From 8e1c59729905fb89a8764ace3dfa0d04119d273e Mon Sep 17 00:00:00 2001
From: Zequan Wu
Date: Wed, 25 Sep 2024 15:59:29 -0700
Subject: [PATCH 1/2] [lldb][DWARF] Replace lldb's DWARFDebugArangeSet with
llvm's
https://github.com/adrian-prantl updated
https://github.com/llvm/llvm-project/pull/106442
>From 9f4ba3fdb8b144736e51134ced3019a2c57ca861 Mon Sep 17 00:00:00 2001
From: Adrian Prantl
Date: Wed, 28 Aug 2024 10:04:33 -0700
Subject: [PATCH] [lldb] Store expression evaluator diagnostics in an
llvm:
https://github.com/DavidSpickett approved this pull request.
LGTM
In theory we could test this but it'd be platform specific and error injection
is always tricky, the change is straightforward, so let's not worry about it.
https://github.com/llvm/llvm-project/pull/106950
__
Author: dlav-sc
Date: 2024-09-25T10:13:40+01:00
New Revision: c93e29439b1ab8ef6873c385f152a06e3395cb59
URL:
https://github.com/llvm/llvm-project/commit/c93e29439b1ab8ef6873c385f152a06e3395cb59
DIFF:
https://github.com/llvm/llvm-project/commit/c93e29439b1ab8ef6873c385f152a06e3395cb59.diff
LOG:
https://github.com/DavidSpickett closed
https://github.com/llvm/llvm-project/pull/106950
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
DavidSpickett wrote:
Feels like we diverted you from your original problem though, which was the
remote taking the informative errno and changing it to some meaningless value.
If you've solved your problem then no obligation to do any more but if you do
want to look into the other reporting me
DavidSpickett wrote:
We're almost there for the save all / restore all anyway. We'll need special
cases for SME of course but SME is weird enough to justify that.
https://github.com/llvm/llvm-project/pull/106695
___
lldb-commits mailing list
lldb-comm
Author: David Spickett
Date: 2024-09-25T10:27:57+01:00
New Revision: 5ee2deac0c3b85deaeb0031b4030db99d266abdc
URL:
https://github.com/llvm/llvm-project/commit/5ee2deac0c3b85deaeb0031b4030db99d266abdc
DIFF:
https://github.com/llvm/llvm-project/commit/5ee2deac0c3b85deaeb0031b4030db99d266abdc.diff
DavidSpickett wrote:
> There will be more features in future meaning more read/ write routines doing
> almost similar stuff.
IMO We may later consider refactoring the code to provide a top level interface
for feature registers read and write.
Yes I would like a "data driven" model for it. I go
https://github.com/DavidSpickett closed
https://github.com/llvm/llvm-project/pull/106695
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: David Spickett
Date: 2024-09-25T10:08:10+01:00
New Revision: 706821ba8ff9db829252581dd12d8c5ee2e7b3f0
URL:
https://github.com/llvm/llvm-project/commit/706821ba8ff9db829252581dd12d8c5ee2e7b3f0
DIFF:
https://github.com/llvm/llvm-project/commit/706821ba8ff9db829252581dd12d8c5ee2e7b3f0.diff
labath wrote:
> Is the following correct: Even if the user does not have debug symbols
> installed, it would always be sufficient to match the **first** named frame.
That *might* work. The complication is that the name of the "first named frame"
will different depending on whether you have deb
https://github.com/omjavaid approved this pull request.
This looks good to me. I haven't tested it myself though.
Just one thing that's bothering me is that we are now gradually implementing a
number of similar functions to read/write feature registers like ZT ZA or FPMR
etc.
There will be m
labath wrote:
Yeah, the thing which makes the core files different from live processes is
that core files (at least minidumps, the situation is a bit fuzzier for elf
cores) often have a better idea of where the files are located. OTOH, the
dynamic loader plugin is a (I'm deliberately not using
jimingham wrote:
> On Sep 24, 2024, at 10:25 AM, Adrian Vogelsgesang ***@***.***> wrote:
>
>
> However, with these new "hiding frame" recognizers, we are using the frame
> hiding recognizers to handle "step out past hidden frames". So if - as was
> done in the original implementation - we'r
jimingham wrote:
> On Sep 25, 2024, at 10:33 AM, Jim Ingham ***@***.***> wrote:
>
>>
>>
>>
>>> On Sep 24, 2024, at 10:25 AM, Adrian Vogelsgesang ***@***.***> wrote:
>>>
>>>
>>> However, with these new "hiding frame" recognizers, we are using the frame
>>> hiding recognizers to handle "st
@@ -224,6 +224,14 @@ const char *Status::AsCString(const char
*default_error_str) const {
if (!m_string.empty() && m_string[m_string.size() - 1] == '\n')
m_string.pop_back();
+ // FIXME: Workaround for ErrorList[ExpressionError, ...].
+ if (m_error.isA()) {
+w
Author: Jonas Devlieghere
Date: 2024-09-25T10:17:09-07:00
New Revision: b3b6141ba1105ad5b9712a9c93891003170c32ac
URL:
https://github.com/llvm/llvm-project/commit/b3b6141ba1105ad5b9712a9c93891003170c32ac
DIFF:
https://github.com/llvm/llvm-project/commit/b3b6141ba1105ad5b9712a9c93891003170c32ac.d
jasonmolenda wrote:
> Feels like we diverted you from your original problem though, which was the
> remote taking the informative errno and changing it to some meaningless value.
It should do that though, shouldn't it? We look up the ERRNO constant we got
in the GDBRemoteErrno table, sending
https://github.com/JDevlieghere updated
https://github.com/llvm/llvm-project/pull/108495
>From 2bf9eaf7e01293e6c1f388daf14cb8099314a5cf Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Wed, 25 Sep 2024 11:04:56 -0700
Subject: [PATCH] [lldb] Introduce an always-on system log category/chann
JDevlieghere wrote:
Rebased + addressed @labath and @adrian-prantl's feedback.
https://github.com/llvm/llvm-project/pull/108495
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -224,6 +224,14 @@ const char *Status::AsCString(const char
*default_error_str) const {
if (!m_string.empty() && m_string[m_string.size() - 1] == '\n')
m_string.pop_back();
+ // FIXME: Workaround for ErrorList[ExpressionError, ...].
+ if (m_error.isA()) {
+w
@@ -61,8 +65,50 @@ std::string DiagnosticManager::GetString(char separator) {
stream << message.drop_front(severity_pos + severity.size());
stream << separator;
}
+ return str;
+}
- return ret;
+void DiagnosticManager::Dump(Log *log) {
+ if (!log)
+return;
@@ -90,9 +79,28 @@ class LibCXXFrameRecognizer : public StackFrameRecognizer {
if (!sc.function)
return {};
-for (RegularExpression &r : m_hidden_regex)
- if (r.Execute(sc.function->GetNameNoArguments()))
+// Check if we have a regex match
+for (Regu
https://github.com/Michael137 approved this pull request.
https://github.com/llvm/llvm-project/pull/108870
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/DavidSpickett created
https://github.com/llvm/llvm-project/pull/109934
The FP8 formats have a "_" in the name so that they are:
1. Easier to read.
2. Possible to use in register expressions if/when they are supported.
Some other bits do have defined meanings but they are not
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: David Spickett (DavidSpickett)
Changes
The FP8 formats have a "_" in the name so that they are:
1. Easier to read.
2. Possible to use in register expressions if/when they are supported.
Some other bits do have defined meanings but they are
DavidSpickett wrote:
Core files will be the next PR and a test will be added to ensure fields show
up when using a core file too.
https://github.com/llvm/llvm-project/pull/109934
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.
@@ -374,25 +377,40 @@ void DebugNamesDWARFIndex::GetFullyQualifiedType(
m_fallback.GetFullyQualifiedType(context, callback);
}
+bool DebugNamesDWARFIndex::SameAsEntryATName(
+llvm::StringRef query_name, const DebugNames::Entry &entry) const {
+ auto maybe_dieoffset = en
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -25,7 +25,6 @@ def setUp(self):
oslist=["windows"],
bugnumber="llvm.org/pr24527. Makefile.rules doesn't know how to build
static libs on Windows",
)
-@expectedFailureAll(remote=True)
dzhidzhoev wrote:
I thought it failed because of
@@ -25,7 +25,6 @@ def setUp(self):
oslist=["windows"],
bugnumber="llvm.org/pr24527. Makefile.rules doesn't know how to build
static libs on Windows",
)
-@expectedFailureAll(remote=True)
dzhidzhoev wrote:
https://lab.llvm.org/staging/#
@@ -25,7 +25,6 @@ def setUp(self):
oslist=["windows"],
bugnumber="llvm.org/pr24527. Makefile.rules doesn't know how to build
static libs on Windows",
)
-@expectedFailureAll(remote=True)
DavidSpickett wrote:
Ok fair enough, maybe it's
https://github.com/DavidSpickett approved this pull request.
Decide what to do with the remote test change but otherwise this LGTM.
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/109961
>From 025276a52939c4091181dea5f633e443c908c4ef Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Mon, 16 Sep 2024 17:48:15 +0200
Subject: [PATCH 1/3] [lldb][test] Use tools from llvm instead of
compi
@@ -25,7 +25,6 @@ def setUp(self):
oslist=["windows"],
bugnumber="llvm.org/pr24527. Makefile.rules doesn't know how to build
static libs on Windows",
)
-@expectedFailureAll(remote=True)
dzhidzhoev wrote:
Fixed
https://github.com/llvm
dzhidzhoev wrote:
> Decide what to do with the remote test change but otherwise this LGTM.
Some other tests are unexpectedly passing on remote config, so they'll need
extra attention.
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits
Author: Vladislav Dzhidzhoev
Date: 2024-09-25T16:19:02+02:00
New Revision: aea06684992873f70c5834e2f455f913e5b8d671
URL:
https://github.com/llvm/llvm-project/commit/aea06684992873f70c5834e2f455f913e5b8d671
DIFF:
https://github.com/llvm/llvm-project/commit/aea06684992873f70c5834e2f455f913e5b8d67
https://github.com/dzhidzhoev closed
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: David Spickett
Date: 2024-09-25T14:31:57Z
New Revision: 26e0b5077236064d9ab0548e049dffce4d476c06
URL:
https://github.com/llvm/llvm-project/commit/26e0b5077236064d9ab0548e049dffce4d476c06
DIFF:
https://github.com/llvm/llvm-project/commit/26e0b5077236064d9ab0548e049dffce4d476c06.diff
LOG
@@ -393,125 +362,222 @@ int main_platform(int argc, char *argv[]) {
lldb_private::Args inferior_arguments;
inferior_arguments.SetArguments(argc, const_cast(argv));
+ Socket::SocketProtocol protocol = Socket::ProtocolUnixDomain;
+
if (fd != SharedSocket::kInvalidFD) {
https://github.com/vogelsgesang closed
https://github.com/llvm/llvm-project/pull/109485
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Adrian Vogelsgesang
Date: 2024-09-25T13:49:42+02:00
New Revision: 786dc5a2da9bb55d98c65d018de25d9bd31485ff
URL:
https://github.com/llvm/llvm-project/commit/786dc5a2da9bb55d98c65d018de25d9bd31485ff
DIFF:
https://github.com/llvm/llvm-project/commit/786dc5a2da9bb55d98c65d018de25d9bd31485ff
@@ -90,9 +79,28 @@ class LibCXXFrameRecognizer : public StackFrameRecognizer {
if (!sc.function)
return {};
-for (RegularExpression &r : m_hidden_regex)
- if (r.Execute(sc.function->GetNameNoArguments()))
+// Check if we have a regex match
+for (Regu
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -161,6 +165,11 @@ def getToolchainUtil(util_name):
}
utils = []
+# Required by API TestBSDArchives.py tests.
+# TODO don't forget to fix the test's Makefile when porting to mainline
DavidSpickett wrote:
TODO left in
https:/
@@ -149,9 +153,9 @@ def getToolchainSpec(self, compiler):
cc_dir = cc_path.parent
def getToolchainUtil(util_name):
-return cc_dir / (cc_prefix + util_name + cc_ext)
+return os.path.join(configuration.llvm_tools_dir, util_name +
exe_ext)
@@ -25,7 +25,6 @@ def setUp(self):
oslist=["windows"],
bugnumber="llvm.org/pr24527. Makefile.rules doesn't know how to build
static libs on Windows",
)
-@expectedFailureAll(remote=True)
DavidSpickett wrote:
And this works now because.
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/DavidSpickett commented:
My only question here is, is there some tool that every bot is going to have to
add an override for because it's not something in `/bin`?
If there is such a tool, that doesn't make this change bad, but we may want to
delay while that's accounted for.
https://github.com/dzhidzhoev updated
https://github.com/llvm/llvm-project/pull/109961
>From 025276a52939c4091181dea5f633e443c908c4ef Mon Sep 17 00:00:00 2001
From: Vladislav Dzhidzhoev
Date: Mon, 16 Sep 2024 17:48:15 +0200
Subject: [PATCH 1/2] [lldb][test] Use tools from llvm instead of
compi
DavidSpickett wrote:
A better version of my question, do you have a list of tools this effects, is
it just the ones where you have modified lines in this PR?
If so we probably have nothing to worry about.
https://github.com/llvm/llvm-project/pull/109961
dzhidzhoev wrote:
> A better version of my question, do you have a list of tools this effects, is
> it just the ones where you have modified lines in this PR?
>
> If so we probably have nothing to worry about.
These are the tools listed in util_names dictionary
https://github.com/llvm/llvm-pr
dlav-sc wrote:
@lhames could you take a look, please?
https://github.com/llvm/llvm-project/pull/99336
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/vogelsgesang updated
https://github.com/llvm/llvm-project/pull/108870
>From 04daaac0eade25a439856bbb287e15860aba1dfd Mon Sep 17 00:00:00 2001
From: Adrian Vogelsgesang
Date: Tue, 27 Aug 2024 17:34:11 +
Subject: [PATCH 1/9] [lldb][libc++] Hide all libc++ implementation det
@@ -161,6 +165,11 @@ def getToolchainUtil(util_name):
}
utils = []
+# Required by API TestBSDArchives.py tests.
+# TODO don't forget to fix the test's Makefile when porting to mainline
dzhidzhoev wrote:
Thanks!
https://github.
@@ -8,6 +8,7 @@
#include "lldb/Utility/Status.h"
+#include "lldb/Expression/DiagnosticManager.h"
labath wrote:
Definitely not a good idea.
https://github.com/llvm/llvm-project/pull/106470
___
lldb-commits mailing
@@ -486,19 +603,37 @@ bool
CommandObjectExpression::EvaluateExpression(llvm::StringRef expr,
result.SetStatus(eReturnStatusSuccessFinishResult);
} else {
-const char *error_cstr = result_valobj_sp->GetError().AsCString();
-if (error_cstr && error
labath wrote:
> > This seems like it could be problematic for IDEs, if they don't print the
> > error in the same window as the expression being evaluated. The arrows
> > could end up pointing to nowhere, or to the wrong place in the expression
> > (if we don't get the right offset).
>
> Even
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/109961
In #102185, toolchain detection for API tests has been rewritten to Python.
However, tools paths for tests are determined from compiler path.
Here tools are taken from `--llvm-tools-dir` dotest.py argument,
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Vladislav Dzhidzhoev (dzhidzhoev)
Changes
In #102185, toolchain detection for API tests has been rewritten in
Python. However, tools paths for tests are determined from compiler path.
Here tools are taken from `--llvm-tools-dir` dotest.py
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/dzhidzhoev edited
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
dzhidzhoev wrote:
> Is there some tool that every bot is going to have to add an override for
> because it's not something in `/bin`?
AFAIK no. All these tools have llvm alternatives.
https://github.com/llvm/llvm-project/pull/109961
___
lldb-commits
@@ -25,7 +25,6 @@ def setUp(self):
oslist=["windows"],
bugnumber="llvm.org/pr24527. Makefile.rules doesn't know how to build
static libs on Windows",
)
-@expectedFailureAll(remote=True)
DavidSpickett wrote:
Just need a basic explanati
bernhardkaindl wrote:
@davide-q: The patch linked from this comment avoids this issue
https://github.com/llvm/llvm-project/issues/101368:
https://github.com/spack/spack/pull/46504#issuecomment-2372520318
https://github.com/llvm/llvm-project/pull/92865
___
https://github.com/labath edited https://github.com/llvm/llvm-project/pull/98528
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,273 @@
+
+//===-- Telemetry.cpp
-===//
+//
+// 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:
@@ -0,0 +1,273 @@
+
+//===-- Telemetry.cpp
-===//
+//
+// 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:
@@ -0,0 +1,273 @@
+
+//===-- Telemetry.cpp
-===//
+//
+// 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:
@@ -257,8 +257,8 @@ enum StopReason {
};
/// Command Return Status Types.
-enum ReturnStatus {
- eReturnStatusInvalid,
+enum ReturnStatus : int {
labath wrote:
How does this relate to the rest of the patch?
https://github.com/llvm/llvm-project/pull/98528
__
https://github.com/labath commented:
I think it'd be good to separate the general mechanics of creating and managing
a telemetry (telemeter) instance from the details of logging individual
telemetry entries. I.e. one PR for the general infrastructure (maybe include
one simple (startup?) teleme
Jlalond wrote:
> I think that would make sense, though I also think that the current behavior
> (attempting to relocate it also does) -- my core question is: how likely is
> it that the dynamic loader will find the right thread-local for a module
> which was loaded by the process class, if the
https://github.com/JDevlieghere updated
https://github.com/llvm/llvm-project/pull/108495
>From c2d2758c68c661153bae0cda857b4c0cb7eddafe Mon Sep 17 00:00:00 2001
From: Jonas Devlieghere
Date: Wed, 25 Sep 2024 11:04:56 -0700
Subject: [PATCH] [lldb] Introduce an always-on system log category/chann
labath wrote:
The way I see it, there should be no distinction between "loading in a core
file" and "actually loading" a module. "Loading of a module", in the sense that
I'm using it here, consists of two steps:
- adding the module to the target's list of modules (usually via
target.GetOrCreat
@@ -393,125 +362,222 @@ int main_platform(int argc, char *argv[]) {
lldb_private::Args inferior_arguments;
inferior_arguments.SetArguments(argc, const_cast(argv));
+ Socket::SocketProtocol protocol = Socket::ProtocolUnixDomain;
+
if (fd != SharedSocket::kInvalidFD) {
99 matches
Mail list logo
