https://github.com/slydiman updated
https://github.com/llvm/llvm-project/pull/101383
>From 14a653c244ea36233de288ebe67a9f42adaacfc5 Mon Sep 17 00:00:00 2001
From: Dmitry Vasilyev
Date: Wed, 31 Jul 2024 22:02:53 +0400
Subject: [PATCH 1/3] [lldb] Added Pipe::WriteWithTimeout()
Fixed few bugs in
dzhidzhoev wrote:
@labath are there any comments from you that haven't been resolved yet? I feel
that I may be missing something, but I don't see exactly what.
https://github.com/llvm/llvm-project/pull/99266
___
lldb-commits mailing list
lldb-commits@
https://github.com/JDevlieghere approved this pull request.
LGTM, this looks completely unused.
https://github.com/llvm/llvm-project/pull/101981
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/101935
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/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 9fea73110ecc0a13d18e5c52f8e7fa62a9de9ee9
8abb0771e646dfc46d832f03485b288a4be08168 --e
Jlalond wrote:
@hokein Thank you for reverting it, I'll look into what I missed :)
https://github.com/llvm/llvm-project/pull/101770
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Med Ismail Bennani
Date: 2024-08-05T09:35:27-07:00
New Revision: 5689cccead7b70d8eeae4c641e8078e6d3c50b9a
URL:
https://github.com/llvm/llvm-project/commit/5689cccead7b70d8eeae4c641e8078e6d3c50b9a
DIFF:
https://github.com/llvm/llvm-project/commit/5689cccead7b70d8eeae4c641e8078e6d3c50b9a.
https://github.com/medismailben closed
https://github.com/llvm/llvm-project/pull/101935
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -1302,6 +1298,36 @@ CommandObject *CommandInterpreter::GetUserCommandObject(
return {};
}
+CommandObject *CommandInterpreter::GetAliasCommandObject(
+llvm::StringRef cmd, StringList *matches, StringList *descriptions) const {
+ std::string cmd_str(cmd);
+ auto find_
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/101778
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Matej =?utf-8?q?Košík?=
Message-ID:
In-Reply-To:
https://github.com/sedymrak updated
https://github.com/llvm/llvm-project/pull/101981
>From 8abb0771e646dfc46d832f03485b288a4be08168 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Matej=20Ko=C5=A1=C3=ADk?=
Date: Mon, 5 Aug 2024 13:47:02 +0200
Subject
@@ -336,3 +336,52 @@ TEST(MinidumpYAML, ExceptionStream_ExtraParameter) {
0xab, 0xad, 0xca, 0xfe}),
*ExpectedContext);
}
+
+TEST(MinidumpYAML, MemoryRegion_64bit) {
+ SmallString<0> Storage;
+ auto ExpectedFile = toBinary(Storage, R"
@@ -373,7 +373,6 @@ void yaml::MappingContextTraits::mapping(
void yaml::MappingContextTraits::mapping(
IO &IO, MemoryDescriptor_64 &Memory, BinaryRef &Content) {
mapRequiredHex(IO, "Start of Memory Range", Memory.StartOfMemoryRange);
- mapRequiredHex(IO, "Data Size", Me
bolshakov-a wrote:
No, IWYU has some complex logic to figure out which type components the type
alias author intends to provide, and which should be `#include`d at the use
site. Of course, substituted template type arguments are the user
responsibility, not the alias author's one, hence this i
Jlalond wrote:
> I see you ended up not using the fallible_iterator thing in the end. I'm sort
> of ok with that, though I think it'd be better to do it that way, as we
> wouldn't need the upfront array bounds check and we could return partial data
> where it made sense,
@labath for this I ne
https://github.com/Jlalond created
https://github.com/llvm/llvm-project/pull/102018
… Options. (#100443)"
This reverts commit 3e4af616334eae532f308605b89ff158dd195180.
@adrian-prantl FYI
Reverts #100443
>From c2eb655327120d794c49a21908c5c664f3283f92 Mon Sep 17 00:00:00 2001
From: Jacob Lalo
@@ -578,7 +657,12 @@ static void SetupImportStdModuleLangOpts(CompilerInstance
&compiler) {
lang_opts.GNUMode = true;
lang_opts.GNUKeywords = true;
lang_opts.CPlusPlus11 = true;
- lang_opts.BuiltinHeadersInSystemModules = true;
+
+ // FIXME: We should use the driver to
@@ -561,7 +562,85 @@ static void SetupLangOpts(CompilerInstance &compiler,
lang_opts.NoBuiltin = true;
}
-static void SetupImportStdModuleLangOpts(CompilerInstance &compiler) {
+// NOTE: should be kept in sync with sdkSupportsBuiltinModules in
+// Toolchains/Darwin.cpp
+stat
@@ -561,7 +562,85 @@ static void SetupLangOpts(CompilerInstance &compiler,
lang_opts.NoBuiltin = true;
}
-static void SetupImportStdModuleLangOpts(CompilerInstance &compiler) {
+// NOTE: should be kept in sync with sdkSupportsBuiltinModules in
+// Toolchains/Darwin.cpp
+stat
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Jacob Lalonde (Jlalond)
Changes
… Options. (#100443)"
This reverts commit 3e4af616334eae532f308605b89ff158dd195180.
@adrian-prantl FYI
Reverts #100443
---
Patch is 40.32 KiB, truncated to 20.00 KiB below, full version:
https://github.
Author: Jacob Lalonde
Date: 2024-08-05T10:17:25-07:00
New Revision: accf5c9bb3b5fe88628a44062a5c0c2f903fca2c
URL:
https://github.com/llvm/llvm-project/commit/accf5c9bb3b5fe88628a44062a5c0c2f903fca2c
DIFF:
https://github.com/llvm/llvm-project/commit/accf5c9bb3b5fe88628a44062a5c0c2f903fca2c.diff
https://github.com/Jlalond closed
https://github.com/llvm/llvm-project/pull/102018
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/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 72c9e24ed92149e853fc215cdf07e3afe34ae146
c2eb655327120d794c49a21908c5c664f3283f92 --e
jimingham wrote:
IIUC, you are adding a new rule that if an incoming command name has partial
matches to one user command and one alias command, the user command is
preferred over the alias command. Is that right?
You certainly should document that rule somewhere - maybe in the Tutorial
sect
mizvekov wrote:
The basic premise here was implemented back in D134604, and this has been for
a few years applied in some cases, like substitution of default arguments.
We leave a Subst* node behind with the purpose of somewhere down the line
changing it back to what the user wrote.
So we do
medismailben wrote:
> IIUC, you are adding a new rule that if an incoming command name has partial
> matches to one user command and one alias command, the user command is
> preferred over the alias command. Is that right?
Yes.
> You certainly should document that rule somewhere - maybe in th
https://github.com/jimingham approved this pull request.
Makes sense, none of this is Python specific so the name is not appropriate.
https://github.com/llvm/llvm-project/pull/101931
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lis
Author: Med Ismail Bennani
Date: 2024-08-05T10:43:42-07:00
New Revision: 039cfe812c15c8f9e52ddb8cfc183fd8c927dba5
URL:
https://github.com/llvm/llvm-project/commit/039cfe812c15c8f9e52ddb8cfc183fd8c927dba5
DIFF:
https://github.com/llvm/llvm-project/commit/039cfe812c15c8f9e52ddb8cfc183fd8c927dba5.
https://github.com/medismailben closed
https://github.com/llvm/llvm-project/pull/101931
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
medismailben wrote:
> This is for this sort of lookup:
>
> ```
> (lldb) reg read pc
> ```
>
> Right? As opposed to tab completion.
Right, tab completion already can suggest multiple candidates, so that worked
already.
> This needs a test case or at least a clear example as a comment in the c
https://github.com/hekota closed https://github.com/llvm/llvm-project/pull/97362
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -395,6 +396,11 @@ class ThreadPlan : public
std::enable_shared_from_this,
bool IsControllingPlan() { return m_is_controlling_plan; }
+ // Returns true if this plan is a leaf plan, meaning the plan will be popped
jimingham wrote:
Leaf plans are only au
mizvekov wrote:
One possibility here is that if you have the type, then you will have a
template specialization type for the template alias, and that gives you the
template arguments used to specialize the alias. Which should answer this need.
But of course, if you have a lossy semantic adjust
@@ -813,12 +819,17 @@ bool Thread::ShouldStop(Event *event_ptr) {
// decide whether they still need to do more work.
bool done_processing_current_plan = false;
-
if (!current_plan->PlanExplainsStop(event_ptr)) {
if (current_plan->TracerExplainsStop()) {
done
jimingham wrote:
Ack, sorry, I missed that you had updated this. My notifications from GitHub
are somewhat flakey...
I didn't understand why you are checking both "IsLeafPlan" and
"MischiefManaged", why does MischiefManaged get to override IsLeafPlan?
https://github.com/llvm/llvm-project/pul
bolshakov-a wrote:
> One possibility here is that if you have the type, then you will have a
> template specialization type for the template alias, and that gives you the
> template arguments used to specialize the alias. Which should answer this
> need.
This can probably go, thank you!
http
Author: Dmitry Vasilyev
Date: 2024-08-05T22:11:24+04:00
New Revision: ddb9869dd2b5c54fc2369287299e11b9a618d71a
URL:
https://github.com/llvm/llvm-project/commit/ddb9869dd2b5c54fc2369287299e11b9a618d71a
DIFF:
https://github.com/llvm/llvm-project/commit/ddb9869dd2b5c54fc2369287299e11b9a618d71a.dif
https://github.com/slydiman closed
https://github.com/llvm/llvm-project/pull/101383
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/slydiman edited
https://github.com/llvm/llvm-project/pull/101283
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: sedymrak
Date: 2024-08-05T11:23:57-07:00
New Revision: 248c53429427034f45705af60d47f3b1090c4799
URL:
https://github.com/llvm/llvm-project/commit/248c53429427034f45705af60d47f3b1090c4799
DIFF:
https://github.com/llvm/llvm-project/commit/248c53429427034f45705af60d47f3b1090c4799.diff
LOG:
Matej =?utf-8?q?Košík?=
Message-ID:
In-Reply-To:
https://github.com/JDevlieghere closed
https://github.com/llvm/llvm-project/pull/101981
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-co
Matej =?utf-8?q?Košík?=
Message-ID:
In-Reply-To:
github-actions[bot] wrote:
@sedymrak Congratulations on having your first Pull Request (PR) merged into
the LLVM Project!
Your changes will be combined with recent changes from other authors, then
tested
by our [build bots](https://lab.llvm
jimingham wrote:
> > IIUC, you are adding a new rule that if an incoming command name has
> > partial matches to one user command and one alias command, the user command
> > is preferred over the alias command. Is that right?
>
> Yes.
>
> > You certainly should document that rule somewhere -
clayborg wrote:
> @hokein Can you share the build command you got to trigger the above msan
> error? I'm having trouble reproducing your issue
And was your build using msan? or just a regular build? I can see a msan build
fail to create a core file due to it crashing, and then you might see th
@@ -1003,6 +1010,21 @@ class Platform : public PluginInterface {
FileSpec GetModuleCacheRoot();
};
+class PlatformMetadata {
+public:
+ PlatformMetadata(Debugger &debugger, const ScriptedMetadata metadata);
+ ~PlatformMetadata() = default;
+
+ Debugger &GetDebugger() cons
@@ -29,3 +29,15 @@ and executable type. If the architecture or executable type
do not match,
a suitable platform will be found automatically."
) lldb::SBPlatform;
+
+%feature("docstring", "
+Create a platform instance using a specific platform plugin name, debugger,
+script n
@@ -180,7 +184,19 @@ class CommandObjectPlatformSelect : public
CommandObjectParsed {
m_interpreter, ArchSpec(), select, error, platform_arch));
if (platform_sp) {
GetDebugger().GetPlatformList().SetSelectedPlatform(platform_sp);
-
+ Opti
@@ -100,6 +99,9 @@ class LLDB_API SBPlatform {
SBPlatform(const char *platform_name);
+ SBPlatform(const char *platform_name, const SBDebugger &debugger,
+ const char *script_name, const SBStructuredData &dict);
+
clayborg wrote:
is `script_na
@@ -0,0 +1,108 @@
+"""
+Test python scripted platform in lldb
+"""
+
+import os, shutil
+
+import lldb
+from lldbsuite.test.decorators import *
+from lldbsuite.test.lldbtest import *
+from lldbsuite.test import lldbutil
+from lldbsuite.test import lldbtest
+
+
+class ScriptedPlatf
@@ -111,6 +111,7 @@ class SBStructuredData {
protected:
friend class SBAttachInfo;
friend class SBLaunchInfo;
+ friend class SBPlatform;
friend class SBDebugger;
friend class SBTarget;
friend class SBProcess;
clayborg wrote:
We keep friending new
@@ -6,20 +6,27 @@
class MyScriptedPlatform(ScriptedPlatform):
def __init__(self, exe_ctx, args):
-self.processes = {}
-
-proc = {}
-proc["name"] = "a.out"
-proc["arch"] = "arm64-apple-macosx"
-proc["pid"] = 420
-proc["parent"
clayborg wrote:
Was this why we saw some Swift progress dialogs hanging around forever?
Looks ok to me. @JDevlieghere feel free to add any more reviewers that have
been working on progress dialogs.
https://github.com/llvm/llvm-project/pull/102097
___
@@ -0,0 +1,58 @@
+// REQUIRES: system-linux, native
clayborg wrote:
I added a test with an on disk file
https://github.com/llvm/llvm-project/pull/101237
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https:/
https://github.com/labath approved this pull request.
This looks fine. Thanks for the reminder.
https://github.com/llvm/llvm-project/pull/99266
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/ll
101 - 154 of 154 matches
Mail list logo
