@@ -0,0 +1,459 @@
+//===-- DILAST.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:
@@ -0,0 +1,459 @@
+//===-- DILAST.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:
https://github.com/labath commented:
I still have a lot of comments, but I think we're making progress.
The most important questions are about the parts where we appear to be
reimplementing some existing lldb functionality. Basically all of the
functionality for looking up names (for members,
https://github.com/labath edited https://github.com/llvm/llvm-project/pull/95738
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,459 @@
+//===-- DILAST.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:
https://github.com/DavidSpickett closed
https://github.com/llvm/llvm-project/pull/90059
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
DavidSpickett wrote:
Custom printing code for just enums for registers would be possible but it
means copying a lot of existing code. A callback reduces that to a copy of
`DumpEnumValue` only. Or you can iterate the value object yourself but then you
have to provide the surrounding format too
labath wrote:
> > The way this would work is by letting the platform instance
> > delegate/upgrate/convert the platform connection into a gdbserver one. The
> > way this would work would be something like this:
> >
> > 1. `lldb-server platform` would advertise (say in `qSupported`) its
slydiman wrote:
> I'd like to hear your opinion on my port mapping alternative.
https://github.com/llvm/llvm-project/pull/100670#issuecomment-2255991921
https://github.com/llvm/llvm-project/pull/100659
___
lldb-commits mailing list
slydiman wrote:
> The way this would work is by letting the platform instance
> delegate/upgrate/convert the platform connection into a gdbserver one. The
> way this would work would be something like this:
>
> 1. `lldb-server platform` would advertise (say in `qSupported`) its support
> for
DavidSpickett wrote:
> So instead of using enum for the field why not a union of enum and unsigned.
The union idea sort of works, but it's clunky enough I'm not going to pursue
it. The most verbose version:
```
fpcr = 0x
= {
<...>
RMode = (meaning = RN, value
labath wrote:
> > Ok, so if I'm reading this right you're saying you saw no ETXTBSY errors
> > with the current implementation --server flag. Is that correct ?
>
> Right. Initially I have marked #100670 as dependent on this.
>
> Ok, agreed. So, we can try to use O_CLOFORK. And simple solution
slydiman wrote:
> Ok, so if I'm reading this right you're saying you saw no ETXTBSY errors with
> the current implementation --server flag. Is that correct ?
Right. Initially I have marked #100670 as dependent on this.
Ok, agreed. So, we can try to use O_CLOFORK.
And simple solution is to
labath wrote:
> > that could mean that something like `$CC hello.cc && ./a.out` could fail
> > (what we're doing here isn't fundamentally different than that).
>
> The difference is that cc creates a.out and exits itself. But `lldb-server
> platform` is still running after creating the
labath wrote:
> > Does this refer the the forking implementation you get with the --server
> > flag, or the serial implementation which only handles one connection at a
> > time (without the flag)?
>
> I mean the `--server` flag. It is very hard to reproduce this issue with the
> serial
slydiman wrote:
See also https://github.com/golang/go/issues/22315
https://github.com/llvm/llvm-project/pull/100659
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
slydiman wrote:
> that could mean that something like `$CC hello.cc && ./a.out` could fail
> (what we're doing here isn't fundamentally different than that).
The difference is that cc creates a.out and exits itself. But `lldb-server
platform` is still running after creating the executable.
labath wrote:
> > If this is only really used for a "only for few requests via the platform
> > protocol", then why not make the CWD a property of the platform object?
> > (Either through a virtual filesystem, or just by having it as a string, and
> > resolving things explicitly)
>
> It is
slydiman wrote:
> Does this refer the the forking implementation you get with the --server
> flag, or the serial implementation which only handles one connection at a
> time (without the flag)?
I mean the `--server` flag. It is very hard to reproduce this issue with the
serial implementation
labath wrote:
I like this idea a lot, but I have some reservations about the implementation.
For one, I think this patch is too big. I once heard someone say "if you have
bullet points in your patch description, then the patch is doing too much".
While I don't think we should go as far as to
slydiman wrote:
> If this is only really used for a "only for few requests via the platform
> protocol", then why not make the CWD a property of the platform object?
> (Either through a virtual filesystem, or just by having it as a string, and
> resolving things explicitly)
It is possible to
https://github.com/labath commented:
Could we standardize on `$(OBJCOPY) --strip-debug` instead?
https://github.com/llvm/llvm-project/pull/100836
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://github.com/labath approved this pull request.
https://github.com/llvm/llvm-project/pull/99012
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
labath wrote:
> @labath
>
> > I wanted to change this code to use threads for a long time, but the idea
> > of using a per-thread virtual file system absolutely terrifies me. That
> > only works is all of the accesses go through the file system (no direct
> > syscalls) and if we're very
@@ -324,6 +324,18 @@ Status PipePosix::ReadWithTimeout(void *buf, size_t size,
bytes_read += result;
if (bytes_read == size || result == 0)
break;
+
+// This is the workaround for the following bug in Linux multithreading
+// select()
tschuett wrote:
I heard rumours that you know a bit about ELF :)
https://github.com/llvm/llvm-project/pull/100900
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
DavidSpickett wrote:
This seems fine, but what happens currently? Does it try to use a tool that's
built for the remote not the host?
https://github.com/llvm/llvm-project/pull/100836
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://github.com/Michael137 closed
https://github.com/llvm/llvm-project/pull/100710
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Michael Buch
Date: 2024-07-29T09:35:00+01:00
New Revision: d72c8b02802c87386f5db3c7de6c79e921618fa3
URL:
https://github.com/llvm/llvm-project/commit/d72c8b02802c87386f5db3c7de6c79e921618fa3
DIFF:
https://github.com/llvm/llvm-project/commit/d72c8b02802c87386f5db3c7de6c79e921618fa3.diff
@@ -456,21 +492,15 @@ ifeq (1, $(USE_SYSTEM_STDLIB))
endif
CXXFLAGS += -nostdlib++ -nostdinc++ -cxx-isystem
$(SDKROOT)/usr/include/c++/v1
LDFLAGS += -L$(SDKROOT)/usr/lib -Wl,-rpath,$(SDKROOT)/usr/lib -lc++
+else
+ifneq (,$(findstring
https://github.com/labath approved this pull request.
https://github.com/llvm/llvm-project/pull/100710
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
labath wrote:
> * thread 1 opens a file for writing (file descriptor A) and starts writing it
>
> * thread 2 starts launching a gdb server. It calls fork(), which creates
> another process with a copy of fd A (the fd has the CLOEXEC flag set, but not
> CLOFORK (the flag doesn't exist))
>
> *
labath wrote:
That *may* be how things works on windows(*), but I'm pretty sure it's not how
things work on linux. A much more likely scenario is:
1. thread 1 opens a file for writing (file descriptor A) and starts writing it
2. thread 2 starts launching a gdb server. It calls fork(), which
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/96538
>From 294246a77e1bb16a34e9451bae65ad340c7ef7a9 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Mon, 29 Jan 2024 16:23:16 +
Subject: [PATCH 1/4] [lldb] Support new libc++ __compressed_pair layout
---
MaskRay wrote:
I'm not familiar with lldb, but I can make some comments as @tschuett invited
me:)
Parsing PT_NOTE is a great step, as program headers are sufficient for
executables, shared objects, and core dumps.
The section header table isn't needed and the relevant code could be dropped
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/99012
>From 709c7c27a67286ab409f5bcc4c9430e025b118e8 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 10 Jul 2024 15:37:45 +0100
Subject: [PATCH 1/4] [WIP][lldb][test] Add a new __compressed_pair layout to
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/96538
>From 294246a77e1bb16a34e9451bae65ad340c7ef7a9 Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Mon, 29 Jan 2024 16:23:16 +
Subject: [PATCH 1/3] [lldb] Support new libc++ __compressed_pair layout
---
https://github.com/Michael137 updated
https://github.com/llvm/llvm-project/pull/99012
>From 242f78b67d6d6ef125b72c9c797fb2686cce280d Mon Sep 17 00:00:00 2001
From: Michael Buch
Date: Wed, 10 Jul 2024 15:37:45 +0100
Subject: [PATCH 1/4] [WIP][lldb][test] Add a new __compressed_pair layout to
https://github.com/tschuett edited
https://github.com/llvm/llvm-project/pull/100900
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,468 @@
+//===-- DILAST.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,468 @@
+//===-- DILAST.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,468 @@
+//===-- DILAST.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,468 @@
+//===-- DILAST.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,468 @@
+//===-- DILAST.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,468 @@
+//===-- DILAST.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,468 @@
+//===-- DILAST.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,468 @@
+//===-- DILAST.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,468 @@
+//===-- DILAST.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,468 @@
+//===-- DILAST.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,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
https://github.com/cmtice edited https://github.com/llvm/llvm-project/pull/95738
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,446 @@
+//===-- DILAST.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:
@@ -0,0 +1,43 @@
+(* LLDB Debug Expressions, a subset of C++ *)
+(* Insired by https://www.nongnu.org/hcb *)
+
+expression = cast_expression;
+
+cast_expression = unary_expression;
+
+unary_expression = postfix_expression
+ | unary_operator cast_expression;
+
@@ -0,0 +1,43 @@
+(* LLDB Debug Expressions, a subset of C++ *)
+(* Insired by https://www.nongnu.org/hcb *)
+
+expression = cast_expression;
+
+cast_expression = unary_expression;
+
+unary_expression = postfix_expression
+ | unary_operator cast_expression;
+
https://github.com/cmtice updated
https://github.com/llvm/llvm-project/pull/95738
>From c703c473147e3e554a98014319294668a0ec790d Mon Sep 17 00:00:00 2001
From: Caroline Tice
Date: Sun, 16 Jun 2024 16:32:47 -0700
Subject: [PATCH 1/4] [LLDB] Add AST node classes, functions, etc. for Data
Author: Med Ismail Bennani
Date: 2024-07-27T18:04:44-07:00
New Revision: bbc457a4f40328452f0c8c8f9b0b5fcb8d286a7b
URL:
https://github.com/llvm/llvm-project/commit/bbc457a4f40328452f0c8c8f9b0b5fcb8d286a7b
DIFF:
Author: Med Ismail Bennani
Date: 2024-07-27T17:30:31-07:00
New Revision: 2402b3213c2f10d5033b31df3a0e59e4ad151fbd
URL:
https://github.com/llvm/llvm-project/commit/2402b3213c2f10d5033b31df3a0e59e4ad151fbd
DIFF:
Author: Med Ismail Bennani
Date: 2024-07-27T15:30:19-07:00
New Revision: 995f643f5aa73d0b73199417b0c87acc07dd44bd
URL:
https://github.com/llvm/llvm-project/commit/995f643f5aa73d0b73199417b0c87acc07dd44bd
DIFF:
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Greg Clayton (clayborg)
Changes
This is the first part in improving ELF core files in LLDB. This first patch
teaches LLDB to get as much data as possible from an in memory ELF image where
we don't have section headers mapped into the
clayborg wrote:
If anyone knows any ELF file experts, please add them as reviewers
https://github.com/llvm/llvm-project/pull/100900
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/clayborg created
https://github.com/llvm/llvm-project/pull/100900
This is the first part in improving ELF core files in LLDB. This first patch
teaches LLDB to get as much data as possible from an in memory ELF image where
we don't have section headers mapped into the
Author: Med Ismail Bennani
Date: 2024-07-27T14:21:18-07:00
New Revision: ecf125eaf0b10f18f4ef27f0ebc20f6ab8108247
URL:
https://github.com/llvm/llvm-project/commit/ecf125eaf0b10f18f4ef27f0ebc20f6ab8108247
DIFF:
Author: Med Ismail Bennani
Date: 2024-07-27T13:36:30-07:00
New Revision: bccff3baeff8164af56e2deee03a0faee93710d0
URL:
https://github.com/llvm/llvm-project/commit/bccff3baeff8164af56e2deee03a0faee93710d0
DIFF:
https://github.com/sayhaan created
https://github.com/llvm/llvm-project/pull/100851
Adds tests to check debug_ranges with an increased batch size and sets previous
test's batch size at 1 to prevent a functional change.
>From ace8031ce49898d2f59b32eb07f2208461da9028 Mon Sep 17 00:00:00 2001
https://github.com/xgupta edited https://github.com/llvm/llvm-project/pull/94844
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/xgupta closed https://github.com/llvm/llvm-project/pull/95675
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Author: Shivam Gupta
Date: 2024-07-27T07:05:44+05:30
New Revision: 558315a0ea8cae8613c3a0061bc6cbe50c5b392f
URL:
https://github.com/llvm/llvm-project/commit/558315a0ea8cae8613c3a0061bc6cbe50c5b392f
DIFF:
https://github.com/llvm/llvm-project/commit/558315a0ea8cae8613c3a0061bc6cbe50c5b392f.diff
@@ -52,6 +52,7 @@ def test_negative_indexing(self):
self.build()
self.validate_negative_indexing()
+@expectedFailureAll(oslist=["windows"], archs=["x86_64"])
kendalharland wrote:
Seems like my Clang invocation is generating different
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: Vladislav Dzhidzhoev (dzhidzhoev)
Changes
Use llvm-strip from llvm tools dir if no path to strip is set. Tests are
changed to use cmake-provided strip.
This is useful for Windows host-Linux remote testing.
---
Full diff:
https://github.com/dzhidzhoev created
https://github.com/llvm/llvm-project/pull/100836
Use llvm-strip from llvm tools dir if no path to strip is set. Tests are
changed to use cmake-provided strip.
This is useful for Windows host-Linux remote testing.
>From
@@ -8001,6 +8001,12 @@ NamedDecl *Sema::ActOnVariableDeclarator(
}
}
+ if (getLangOpts().HLSL) {
+if (R->isHLSLSpecificType() && !NewVD->isImplicit()) {
+ Diag(D.getBeginLoc(), diag::err_hlsl_intangible_type_cannot_be_declared);
llvm-beanz
slydiman wrote:
> One way I can imagine this happening is if the FileSystem instance was local
> to a GDBRemoteCommunicationServerPlatform instance -- rather than the thread
> it happens to be (mostly) running on. This will require more changes to,
> basically, plumb the filesystem instance
@@ -8001,6 +8001,12 @@ NamedDecl *Sema::ActOnVariableDeclarator(
}
}
+ if (getLangOpts().HLSL) {
+if (R->isHLSLSpecificType() && !NewVD->isImplicit()) {
+ Diag(D.getBeginLoc(), diag::err_hlsl_intangible_type_cannot_be_declared);
hekota wrote:
https://github.com/slydiman edited
https://github.com/llvm/llvm-project/pull/100670
___
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/100670
___
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/100670
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -52,6 +52,7 @@ def test_negative_indexing(self):
self.build()
self.validate_negative_indexing()
+@expectedFailureAll(oslist=["windows"], archs=["x86_64"])
kendalharland wrote:
If I change this line:
```
self.runCmd("expr -i 0 --
@@ -52,6 +52,7 @@ def test_negative_indexing(self):
self.build()
self.validate_negative_indexing()
+@expectedFailureAll(oslist=["windows"], archs=["x86_64"])
kendalharland wrote:
Here's the full output with 3e06392 cherry-picked.
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100476
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100476
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -1,3 +1,4 @@
+# XFAIL: target=x86_64-{{.*}}-windows{{.*}}
kendalharland wrote:
I've removed CMAKE_CXX_STANDARD=14 above as it is leftover from debugging and
not correct or necessary.
https://github.com/llvm/llvm-project/pull/100476
kendalharland wrote:
> > ```
> > S:\SourceCache\llvm-project\lldb\test\Shell\Driver\TestConvenienceVariables.test:6:8:
> > error: CHECK: expected string not found in input
> > CHECK: stop reason = breakpoint 1.1
> >^
> > :1:1: note: scanning from here
> > (lldb) command source -s 0
> >
https://github.com/kendalharland closed
https://github.com/llvm/llvm-project/pull/100473
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
@@ -1,3 +1,4 @@
+# XFAIL: target=x86_64-{{.*}}-windows{{.*}}
kendalharland wrote:
For reference, my current setup steps are the following commands run in a
non-admin cmd.exe
```
C:\Program Files\Microsoft Visual
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100476
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/kendalharland edited
https://github.com/llvm/llvm-project/pull/100476
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
301 - 400 of 92210 matches
Mail list logo
