https://github.com/labath edited https://github.com/llvm/llvm-project/pull/91452
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/labath commented:
I am somewhat worried about this slowing down the actual operations it is
reporting progress on. I didn't really measure this, but intuitively, I'd
expect that a one of these operations (parsing/importing one type) would be
pretty fast, and that the whole p
@@ -1411,3 +1414,35 @@ clang::Decl *
ClangASTImporter::ASTImporterDelegate::GetOriginalDecl(clang::Decl *To) {
return m_main.GetDeclOrigin(To).decl;
}
+
+void ClangASTImporter::ASTImporterDelegate::UpdateImportProgress(
labath wrote:
> cast nullptr to a Name
DavidSpickett wrote:
Ok for me to land this or are you still going to check them locally?
https://github.com/llvm/llvm-project/pull/84155
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-com
https://github.com/santhoshe447 created
https://github.com/llvm/llvm-project/pull/91570
Adding a "port" property to the VsCode "attach" command likely extends the
functionality of the debugger configuration to allow attaching to a process
using PID or PORT number.
Currently, the "Attach" confi
github-actions[bot] wrote:
:warning: Python code formatter, darker found issues in your code. :warning:
You can test this locally with the following command:
``bash
darker --check --diff -r
443377a9d1a8d4a69a317a1a892184c59dd0aec6...4774f5803327d766d27c26646927e8ba42368b40
lldb/
https://github.com/santhoshe447 updated
https://github.com/llvm/llvm-project/pull/91570
>From 960351c9abf51f42d92604ac6297aa5b76ddfba5 Mon Sep 17 00:00:00 2001
From: Santhosh Kumar Ellendula
Date: Fri, 17 Nov 2023 15:09:10 +0530
Subject: [PATCH 1/4] [lldb][test] Add the ability to extract the v
https://github.com/santhoshe447 updated
https://github.com/llvm/llvm-project/pull/91570
>From 960351c9abf51f42d92604ac6297aa5b76ddfba5 Mon Sep 17 00:00:00 2001
From: Santhosh Kumar Ellendula
Date: Fri, 17 Nov 2023 15:09:10 +0530
Subject: [PATCH 1/4] [lldb][test] Add the ability to extract the v
https://github.com/santhoshe447 updated
https://github.com/llvm/llvm-project/pull/91570
>From 960351c9abf51f42d92604ac6297aa5b76ddfba5 Mon Sep 17 00:00:00 2001
From: Santhosh Kumar Ellendula
Date: Fri, 17 Nov 2023 15:09:10 +0530
Subject: [PATCH 1/5] [lldb][test] Add the ability to extract the v
https://github.com/santhoshe447 updated
https://github.com/llvm/llvm-project/pull/91570
>From 960351c9abf51f42d92604ac6297aa5b76ddfba5 Mon Sep 17 00:00:00 2001
From: Santhosh Kumar Ellendula
Date: Fri, 17 Nov 2023 15:09:10 +0530
Subject: [PATCH 1/6] [lldb][test] Add the ability to extract the v
https://github.com/tmatheson-arm updated
https://github.com/llvm/llvm-project/pull/90987
>From 4b8b776348438847c2eb238dac973e93fe93294e Mon Sep 17 00:00:00 2001
From: Tomas Matheson
Date: Mon, 29 Apr 2024 19:57:17 +0100
Subject: [PATCH 1/6] [AArch64] move extension information into tablgen
Gen
Author: Pavel Labath
Date: 2024-05-09T11:40:51Z
New Revision: b903badd73a2467fdd4e363231f2bf9b0704b546
URL:
https://github.com/llvm/llvm-project/commit/b903badd73a2467fdd4e363231f2bf9b0704b546
DIFF:
https://github.com/llvm/llvm-project/commit/b903badd73a2467fdd4e363231f2bf9b0704b546.diff
LOG:
labath wrote:
> This looks good to me, I know there are other codepaths that handle this
> correctly, where we can backtrace out of a frameless function that faults
> into a trap handler and we have the entire register state available in the
> trap handler.
>
> Looking at this, I'm a little u
https://github.com/DavidSpickett created
https://github.com/llvm/llvm-project/pull/91585
Instead of updating the member of the ObjectFileELF instance. This means that
if one object file asks another to parse the symbol table, that first object's
address class map is not left empty, which would
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: David Spickett (DavidSpickett)
Changes
Instead of updating the member of the ObjectFileELF instance. This means that
if one object file asks another to parse the symbol table, that first object's
address class map is not left empty, which
@@ -87,8 +105,15 @@ SymbolVendorELF::CreateInstance(const lldb::ModuleSP
&module_sp,
FileSpecList search_paths = Target::GetDefaultDebugFileSearchPaths();
FileSpec dsym_fspec =
PluginManager::LocateExecutableSymbolFile(module_spec, search_paths);
- if (!dsym_fspec)
https://github.com/labath created
https://github.com/llvm/llvm-project/pull/91586
Parsing of '::' scopes in TypeQuery was very naive and failed for names with
'::''s in template arguments. Interestingly, one of the functions it was
calling (Type::GetTypeScopeAndBasename) was already doing the
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Pavel Labath (labath)
Changes
Parsing of '::' scopes in TypeQuery was very naive and failed for names with
'::''s in template arguments. Interestingly, one of the functions it was
calling (Type::GetTypeScopeAndBasename) was already doing t
https://github.com/labath approved this pull request.
The change makes sense to me, but this part here got me worried:
> then asked for a better object file, which returned the same program file
> again
Does this mean that we had two ObjectFileELF instances referring to the same
file on disk f
https://github.com/Michael137 edited
https://github.com/llvm/llvm-project/pull/91586
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -492,12 +494,37 @@ class Type : public std::enable_shared_from_this,
public UserID {
static int Compare(const Type &a, const Type &b);
+ // Represents a parsed type name coming out of GetTypeScopeAndBasename. The
+ // structure holds StringRefs pointing to portions of
https://github.com/Michael137 approved this pull request.
Looks much cleaner now, thanks!
https://github.com/llvm/llvm-project/pull/91586
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-com
labath wrote:
https://lab.llvm.org/buildbot/#/builders/68/builds/73871 is an example of such
a failure.
https://github.com/llvm/llvm-project/pull/91591
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/li
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Pavel Labath (labath)
Changes
lldb-dap was setting a flag which was meant to shut it down as soon as it sent
a terminated event. The problem with this flag is two-fold:
- as far as I can tell (definitely not an expert here), there's no
jus
https://github.com/labath created
https://github.com/llvm/llvm-project/pull/91591
lldb-dap was setting a flag which was meant to shut it down as soon as it sent
a terminated event. The problem with this flag is two-fold:
- as far as I can tell (definitely not an expert here), there's no
justif
DavidSpickett wrote:
We can compare against the path the plugin found, though it's surprising that
the plugins return anything at all so maybe there is a bug there too.
It'll need a new test case, as `TestStringLiteralExpr.test` will no longer hit
the code I'm changing in this PR, so I'll do i
https://github.com/labath updated
https://github.com/llvm/llvm-project/pull/91586
>From ae3d99727f50be66f2ee0f953c88afd6d22ae8bd Mon Sep 17 00:00:00 2001
From: Pavel Labath
Date: Thu, 9 May 2024 10:06:11 +
Subject: [PATCH 1/2] [lldb] Improve type name parsing
Parsing of '::' scopes in Type
https://github.com/DavidSpickett updated
https://github.com/llvm/llvm-project/pull/91585
>From 34c5ac8292b34d96039c6c69326f3fceb5cc3499 Mon Sep 17 00:00:00 2001
From: David Spickett
Date: Thu, 9 May 2024 11:23:32 +
Subject: [PATCH 1/2] [lldb][ELF] Return address class map from symbol table
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/91585
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/DavidSpickett edited
https://github.com/llvm/llvm-project/pull/91585
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
DavidSpickett wrote:
I realised that as it was, the calling object file would get its map updated
but not the other object file. Which is potentially a regression if we choose
to use one or the other file for a lookup. So now the methods update the member
map, and return the changes they made
Author: Zequan Wu
Date: 2024-05-09T10:42:53-04:00
New Revision: fdede92d435068f31e7ea3a1dddb46d50343dd8c
URL:
https://github.com/llvm/llvm-project/commit/fdede92d435068f31e7ea3a1dddb46d50343dd8c
DIFF:
https://github.com/llvm/llvm-project/commit/fdede92d435068f31e7ea3a1dddb46d50343dd8c.diff
LOG
https://github.com/ZequanWu closed
https://github.com/llvm/llvm-project/pull/91343
___
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/91603
Code in https://github.com/llvm/llvm-project/pull/90622 exposed a situation
where a symbol table may be loaded via a second copy of the same object.
This resulted in the first copy having its address class
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: David Spickett (DavidSpickett)
Changes
Code in https://github.com/llvm/llvm-project/pull/90622 exposed a situation
where a symbol table may be loaded via a second copy of the same object.
This resulted in the first copy having its address
DavidSpickett wrote:
Alternative: https://github.com/llvm/llvm-project/pull/91603
https://github.com/llvm/llvm-project/pull/91585
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
DavidSpickett wrote:
The only thing I can think of that breaks this is if some object wanted to use
the same symbol table section, but interpret it in a different way that changed
the address classes. I don't see any evidence of us doing that or needing to.
Even if we did it'd probably change
adrian-prantl wrote:
> I am somewhat worried about this slowing down the actual operations it is
> reporting progress on. I didn't really measure this, but intuitively, I'd
> expect that a one of these operations (parsing/importing one type) would be
> pretty fast, and that the whole process t
adrian-prantl wrote:
I think that would be a good start. Also tagging @jasonmolenda for advice.
https://github.com/llvm/llvm-project/pull/91321
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/ll
@@ -144,6 +144,19 @@ class ProcessInstanceInfo : public ProcessInfo {
long int tv_usec = 0;
};
+ enum class ProcessState {
+Unknown,
+Dead,
+DiskSleep,
+Idle,
+Paging,
+Parked,
+Running,
+Sleeping,
+TracedOrStopped,
+Zombie,
+ };
@@ -254,6 +277,8 @@ class ProcessInstanceInfo : public ProcessInfo {
struct timespec m_system_time {};
struct timespec m_cumulative_user_time {};
struct timespec m_cumulative_system_time {};
+ int8_t m_nice_value = INT8_MAX;
feg208 wrote:
yeah. I'll mak
labath wrote:
> > I am somewhat worried about this slowing down the actual operations it is
> > reporting progress on. I didn't really measure this, but intuitively, I'd
> > expect that a one of these operations (parsing/importing one type) would be
> > pretty fast, and that the whole process
https://github.com/walter-erquinigo approved this pull request.
This all makes sense to me. Thank you!
https://github.com/llvm/llvm-project/pull/91591
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/list
JDevlieghere wrote:
> My understanding was that the progress increment is designed to be really
> cheap (writing two pointers) and that it's up to presentation layer to decide
> a t what frequency to update the UI.
>
> @JDevlieghere — is that perception correct?
You're correct about the prese
@@ -12,6 +12,9 @@
#include "lldb/Utility/ProcessInfo.h"
#include "gtest/gtest.h"
+#include
+#include
feg208 wrote:
yeah. The cmake file enforces a linux-only build as well. However as @jimingham
pointed out someone could plausibly move this into a non-linu
@@ -237,6 +250,16 @@ class ProcessInstanceInfo : public ProcessInfo {
m_cumulative_system_time.tv_usec > 0;
}
+ int8_t GetNiceValue() const { return m_nice_value; }
emaste wrote:
nice and priority are not synonymous though, nice is one input int
https://github.com/jroelofs approved this pull request.
https://github.com/llvm/llvm-project/pull/90987
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/chelcassanova created
https://github.com/llvm/llvm-project/pull/91618
Removes the debugger broadcast bits from `Debugger.h` and instead uses the enum
from `lldb-enumerations.h`. Also adds the `eBroadcastSymbolChange` bit to the
enum in `lldb-enumerations.h`.
>From f338108d6
https://github.com/feg208 updated
https://github.com/llvm/llvm-project/pull/91544
>From 18b0d55d1c4e04842e531c7f7e304998f2b2ad4e Mon Sep 17 00:00:00 2001
From: Fred Grim
Date: Wed, 8 May 2024 15:36:16 -0700
Subject: [PATCH] [lldb] Adds additional fields to ProcessInfo
To implement SaveCore for
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Chelsea Cassanova (chelcassanova)
Changes
Removes the debugger broadcast bits from `Debugger.h` and instead uses the enum
from `lldb-enumerations.h`. Also adds the `eBroadcastSymbolChange` bit to the
enum in `lldb-enumerations.h`.
---
Ful
@@ -117,6 +118,10 @@ bool ProcessInfo::IsScriptedProcess() const {
return m_scripted_metadata_sp && *m_scripted_metadata_sp;
}
+bool ProcessInstanceInfo::NiceValueIsValid() const {
+ return m_nice_value >= PRIO_MIN && m_nice_value <= PRIO_MAX;
feg208 wrote:
@@ -17,6 +17,7 @@
#include
#include
+#include
feg208 wrote:
removed
https://github.com/llvm/llvm-project/pull/91544
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailma
@@ -237,6 +250,16 @@ class ProcessInstanceInfo : public ProcessInfo {
m_cumulative_system_time.tv_usec > 0;
}
+ int8_t GetNiceValue() const { return m_nice_value; }
+
+ void SetNiceValue(int8_t nice_value) { m_nice_value = nice_value; }
+
+ bool NiceValueIsVali
@@ -237,6 +250,16 @@ class ProcessInstanceInfo : public ProcessInfo {
m_cumulative_system_time.tv_usec > 0;
}
+ int8_t GetNiceValue() const { return m_nice_value; }
feg208 wrote:
Done. Agreed. I also added a note in the linux specific code. In l
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 fe0b7983a2f510cdede22cdf6c9227e32ded6a15
f338108d6b0cbb47e72663c58c1cbb17ee446cbc --
https://github.com/JDevlieghere approved this pull request.
LGTM but let's give Alex and Ismail a chance to take a look too.
https://github.com/llvm/llvm-project/pull/91618
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.or
https://github.com/JDevlieghere edited
https://github.com/llvm/llvm-project/pull/91618
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
adrian-prantl wrote:
If this turns out to be necessary, one way to rate-limit them would be to have
a nesting depth counter. Assuming that these imports happen recursively we
could create only Progress objects for the top n layers.
https://github.com/llvm/llvm-project/pull/91452
__
JDevlieghere wrote:
> If this turns out to be necessary, one way to rate-limit them would be to
> have a nesting depth counter. Assuming that these imports happen recursively
> we could create only Progress objects for the top n layers.
Is the code that emits the progress event recursive too?
jasonmolenda wrote:
Will debug this today.
https://github.com/llvm/llvm-project/pull/91321
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/medismailben approved this pull request.
LGTM
https://github.com/llvm/llvm-project/pull/91618
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/medismailben updated
https://github.com/llvm/llvm-project/pull/91109
>From 625245737c31ac4e2cf04417bc8457caa461ef31 Mon Sep 17 00:00:00 2001
From: Med Ismail Bennani
Date: Thu, 9 May 2024 10:02:50 -0700
Subject: [PATCH] [lldb/crashlog] Enforce image loading policy
In `27f27d
https://github.com/bulbazord approved this pull request.
https://github.com/llvm/llvm-project/pull/91109
___
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-05-09T10:13:20-07:00
New Revision: 785b143a402a282822c3d5e30bb4e2b1980c0b1e
URL:
https://github.com/llvm/llvm-project/commit/785b143a402a282822c3d5e30bb4e2b1980c0b1e
DIFF:
https://github.com/llvm/llvm-project/commit/785b143a402a282822c3d5e30bb4e2b1980c0b1e.
https://github.com/medismailben closed
https://github.com/llvm/llvm-project/pull/91109
___
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-05-09T10:19:34-07:00
New Revision: 8585bf7542f1098bd03a667a408d42d2a815d305
URL:
https://github.com/llvm/llvm-project/commit/8585bf7542f1098bd03a667a408d42d2a815d305
DIFF:
https://github.com/llvm/llvm-project/commit/8585bf7542f1098bd03a667a408d42d2a815d305.
https://github.com/medismailben closed
https://github.com/llvm/llvm-project/pull/91162
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/bulbazord approved this pull request.
https://github.com/llvm/llvm-project/pull/91618
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/chelcassanova updated
https://github.com/llvm/llvm-project/pull/91618
>From 167850e01960175e332b9da3d95d6054102a960a Mon Sep 17 00:00:00 2001
From: Chelsea Cassanova
Date: Thu, 9 May 2024 09:23:02 -0700
Subject: [PATCH] [lldb][enums] Remove broadcast bits from debugger
Remov
Author: Chelsea Cassanova
Date: 2024-05-09T10:28:23-07:00
New Revision: b9e3fa84d3fdfe718a4a3085f7adeda3d81f2568
URL:
https://github.com/llvm/llvm-project/commit/b9e3fa84d3fdfe718a4a3085f7adeda3d81f2568
DIFF:
https://github.com/llvm/llvm-project/commit/b9e3fa84d3fdfe718a4a3085f7adeda3d81f2568.d
https://github.com/chelcassanova closed
https://github.com/llvm/llvm-project/pull/91618
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/medismailben updated
https://github.com/llvm/llvm-project/pull/91107
>From d34abd53e2cd8484299516f8c7f01fe45e58e07c Mon Sep 17 00:00:00 2001
From: Med Ismail Bennani
Date: Thu, 9 May 2024 10:35:33 -0700
Subject: [PATCH] [lldb] Verify target stop-hooks support with scripted pr
https://github.com/medismailben closed
https://github.com/llvm/llvm-project/pull/91107
___
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-05-09T10:39:05-07:00
New Revision: b3a835e129ed8a67cf393f9ee26989b36a3eff1c
URL:
https://github.com/llvm/llvm-project/commit/b3a835e129ed8a67cf393f9ee26989b36a3eff1c
DIFF:
https://github.com/llvm/llvm-project/commit/b3a835e129ed8a67cf393f9ee26989b36a3eff1c.
https://github.com/medismailben created
https://github.com/llvm/llvm-project/pull/91631
This patch fixes a bug in when resolving and loading modules from the binary
image list.
When loading a module, we would first use the UUID from the binary image list
with `dsymForUUID` to fetch the dSYM b
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Med Ismail Bennani (medismailben)
Changes
This patch fixes a bug in when resolving and loading modules from the binary
image list.
When loading a module, we would first use the UUID from the binary image list
with `dsymForUUID` to fetch t
@@ -418,9 +418,22 @@ def locate_module_and_debug_symbols(self):
with print_lock:
print('falling back to binary inside "%s"' % dsym)
self.symfile = dsym
-for filename in os.listdi
@@ -418,9 +418,22 @@ def locate_module_and_debug_symbols(self):
with print_lock:
print('falling back to binary inside "%s"' % dsym)
self.symfile = dsym
-for filename in os.listdi
https://github.com/chelcassanova updated
https://github.com/llvm/llvm-project/pull/91404
>From c334f7357aebefa3e0b7af645396e699cf3a4c8d Mon Sep 17 00:00:00 2001
From: Chelsea Cassanova
Date: Thu, 9 May 2024 11:08:29 -0700
Subject: [PATCH] [lldb][breakpoint] Grey out disabled breakpoints
This c
chelcassanova wrote:
I changed this PR to make disabled breakpoints greyed out (per Ismail's
suggestion). Since this is being done at the `Breakpoint` level we have access
to the target and its debugger to access `GetUseColor()`.
https://github.com/llvm/llvm-project/pull/91404
https://github.com/chelcassanova edited
https://github.com/llvm/llvm-project/pull/91404
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/chelcassanova edited
https://github.com/llvm/llvm-project/pull/91404
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/medismailben updated
https://github.com/llvm/llvm-project/pull/91631
>From e2cd9670c20daac3f6a5f75806c7f48ed7b2ccd9 Mon Sep 17 00:00:00 2001
From: Med Ismail Bennani
Date: Thu, 9 May 2024 11:38:03 -0700
Subject: [PATCH] [lldb/crashlog] Fix module binary resolution
This patch
@@ -848,6 +850,13 @@ void Breakpoint::GetDescription(Stream *s,
lldb::DescriptionLevel level,
const size_t num_locations = GetNumLocations();
const size_t num_resolved_locations = GetNumResolvedLocations();
+ // Grey out any disabled breakpoints in the list of breakpoint
https://github.com/medismailben updated
https://github.com/llvm/llvm-project/pull/91631
>From b849720f6559392f91c54be5987beeb8c8c3fe21 Mon Sep 17 00:00:00 2001
From: Med Ismail Bennani
Date: Thu, 9 May 2024 12:39:01 -0700
Subject: [PATCH] [lldb/crashlog] Fix module binary resolution
This patch
@@ -848,6 +850,13 @@ void Breakpoint::GetDescription(Stream *s,
lldb::DescriptionLevel level,
const size_t num_locations = GetNumLocations();
const size_t num_resolved_locations = GetNumResolvedLocations();
+ // Grey out any disabled breakpoints in the list of breakpoint
@@ -418,9 +418,20 @@ def locate_module_and_debug_symbols(self):
with print_lock:
print('falling back to binary inside "%s"' % dsym)
self.symfile = dsym
-for filename in os.listdi
https://github.com/JDevlieghere edited
https://github.com/llvm/llvm-project/pull/91631
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/91631
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -418,9 +418,20 @@ def locate_module_and_debug_symbols(self):
with print_lock:
print('falling back to binary inside "%s"' % dsym)
self.symfile = dsym
-for filename in os.listdi
@@ -418,9 +418,20 @@ def locate_module_and_debug_symbols(self):
with print_lock:
print('falling back to binary inside "%s"' % dsym)
self.symfile = dsym
-for filename in os.listdi
https://github.com/medismailben updated
https://github.com/llvm/llvm-project/pull/91631
>From 1f63d6807bc8a6b1e04cb96cbc7e4fd1572553e4 Mon Sep 17 00:00:00 2001
From: Med Ismail Bennani
Date: Thu, 9 May 2024 12:51:39 -0700
Subject: [PATCH] [lldb/crashlog] Fix module binary resolution
This patch
https://github.com/bulbazord approved this pull request.
https://github.com/llvm/llvm-project/pull/91631
___
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-05-09T13:51:52-07:00
New Revision: f4a7e1f9bac1f11e1db1c0a895f3f681838f89f2
URL:
https://github.com/llvm/llvm-project/commit/f4a7e1f9bac1f11e1db1c0a895f3f681838f89f2
DIFF:
https://github.com/llvm/llvm-project/commit/f4a7e1f9bac1f11e1db1c0a895f3f681838f89f2.
https://github.com/medismailben closed
https://github.com/llvm/llvm-project/pull/91631
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Tomas Matheson
Date: 2024-05-09T21:54:48+01:00
New Revision: 639a740035b732e9bc0f43f3f95d1ce3acf82e1b
URL:
https://github.com/llvm/llvm-project/commit/639a740035b732e9bc0f43f3f95d1ce3acf82e1b
DIFF:
https://github.com/llvm/llvm-project/commit/639a740035b732e9bc0f43f3f95d1ce3acf82e1b.diff
https://github.com/tmatheson-arm closed
https://github.com/llvm/llvm-project/pull/90987
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/medismailben created
https://github.com/llvm/llvm-project/pull/91653
This should fix the various crashlog test failures on the bots:
```
lldb-shell ::
ScriptInterpreter/Python/Crashlog/app_specific_backtrace_crashlog.test
lldb-shell :: ScriptInterpreter/Python/Crashlog/i
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Med Ismail Bennani (medismailben)
Changes
This should fix the various crashlog test failures on the bots:
```
lldb-shell ::
ScriptInterpreter/Python/Crashlog/app_specific_backtrace_crashlog.test
lldb-shell :: ScriptInterpreter/Python/C
https://github.com/JDevlieghere approved this pull request.
https://github.com/llvm/llvm-project/pull/91653
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
1 - 100 of 127 matches
Mail list logo
