labath wrote:
Don't take this to imply I'm against removing the non-native plugin (I'm not,
I'd very much like to get rid of it myself), but here are a couple of
alternatives:
- it has always bothered me that this is controlled by an environment variable.
The original justification was that it
JDevlieghere wrote:
> We agreed that the native parser would be the way forward in the last
> EuroLLVM round-table IIRC (CC @JDevlieghere @labath).
That's right. The problem is that neither implementation is complete, and
things only work because there's an automatic fallback. No matter which
DavidSpickett wrote:
https://github.com/llvm/llvm-project/issues/114906 as well.
https://github.com/llvm/llvm-project/pull/149305
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
Michael137 wrote:
I think as a pre-requisite to this we should remove the non-native PDB parser
(and anything associated with it). That way we wouldn't need any special
environment variable setting etc.
We agreed that the native parser would be the way forward in the last EuroLLVM
round-table
llvmbot wrote:
@llvm/pr-subscribers-lldb
Author: nerix (Nerixyz)
Changes
>From https://github.com/llvm/llvm-project/pull/148554#issuecomment-3083261858
>- this adds an option for API tests to be run with the native PDB reader on
>Windows. As there are a lot of failures with PDB, this is
https://github.com/Nerixyz ready_for_review
https://github.com/llvm/llvm-project/pull/149305
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/149305
>From 457d51e195fd2414424809efd88592884e13272d Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Thu, 17 Jul 2025 15:10:24 +0200
Subject: [PATCH] [LLDB] Run API tests with native PDB too
---
.../Python/lldbsuite/te
Nerixyz wrote:
I made it opt-in now. A test can set `TEST_WITH_PDB_DEBUG_INFO = True`.
Unfortunately, all STL tests currently fail. Most of this is because the
demangled name in the native PDB parser has spaces at different positions than
the DIA parser which I used before.
I'm not sure if it
https://github.com/Nerixyz edited
https://github.com/llvm/llvm-project/pull/149305
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/149305
>From 0c9292538507307467cdf8184c5599dbadb79bb9 Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Thu, 17 Jul 2025 15:10:24 +0200
Subject: [PATCH] [LLDB] Run API tests with native PDB too
---
.../Python/lldbsuite/te
DavidSpickett wrote:
Opened https://github.com/llvm/llvm-project/issues/149498 so you can refer to
it.
I think it's a reasonable pitch to say:
* Formatters that work with PDB are a good idea.
* If we opt-in those formatters for testing using PDB, they will be run on at
least Linaro's Windows o
DavidSpickett wrote:
I ran this on Linaro's bot machine and got these results:
```
Unresolved Tests (5):
lldb-api ::
functionalities/data-formatter/data-formatter-stl/generic/string/TestDataFormatterStdString.py
lldb-api :: lang/c/vla/TestVLA.py
lldb-api :: python_api/
DavidSpickett wrote:
Yes this is what I was thinking of. Don't go diving into the failures yet, I'll
try this on the bot machine first and see if we need other adjustments.
https://github.com/llvm/llvm-project/pull/149305
___
lldb-commits mailing list
Nerixyz wrote:
@DavidSpickett added the PDB tests here - Is the general approach fine?
https://github.com/llvm/llvm-project/pull/149305
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commi
https://github.com/Nerixyz updated
https://github.com/llvm/llvm-project/pull/149305
>From eeea8f973f5583276e4b9c24e8cddfa67b0cf06f Mon Sep 17 00:00:00 2001
From: Nerixyz
Date: Thu, 17 Jul 2025 15:10:24 +0200
Subject: [PATCH] [LLDB] Run API tests with native PDB too
---
.../Python/lldbsuite/te
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 HEAD~1...HEAD
lldb/packages/Python/lldbsuite/test/builders/builder.py
lldb/packages/Pytho
https://github.com/Nerixyz edited
https://github.com/llvm/llvm-project/pull/149305
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/Nerixyz created
https://github.com/llvm/llvm-project/pull/149305
>From https://github.com/llvm/llvm-project/pull/148554#issuecomment-3083261858
>- this runs the API tests with the native PDB on Windows. Using native over
>DIA because it's easier to inspect/debug.
One of the
18 matches
Mail list logo
