Re: [lldb-dev] [Openmp-dev] [Release-testers] 13.0.0-rc3 has been tagged

On Mon, Sep 20, 2021 at 1:14 PM Andrzej Warzynski wrote: > Hi Brian, > > Thank you for helping with the release! > > On 20/09/2021 18:40, Brian Cain via Openmp-dev wrote: > > I also disabled flang (-no-flang) because of > > memory exhaustion while trying to build. Is this increased memory > > co

Re: [lldb-dev] [Openmp-dev] [Release-testers] 13.0.0-rc3 has been tagged

Hi Brian, Thank you for helping with the release! On 20/09/2021 18:40, Brian Cain via Openmp-dev wrote: I also disabled flang (-no-flang) because of memory exhaustion while trying to build.  Is this increased memory consumption expected or could it be a bug? The memory usage of LLVM Flang wa

Re: [lldb-dev] [Release-testers] 13.0.0-rc3 has been tagged

Ubuntu 20 binary uploaded. I also disabled flang (-no-flang) because of memory exhaustion while trying to build. Is this increased memory consumption expected or could it be a bug? $ cat clang+llvm-13.0.0-rc3-x86_64-linux-gnu-ubuntu-20.04.tar.xz.sha256 488ff13c9a54f6b7b2aeb26e930da7d72e32a15542

Re: [lldb-dev] 2021 LLVM Developers' Meeting - Call for Talk Proposals DEADLINE EXTENDED to Sept 27

Hello! This is an update to let you know that the deadline has been extended to September 27th at 5pm PDT. A couple of additional notes: - Notification will be on Oct 8th - Recordings will be happening as early as the first week of November (Nov 1-5). We are finalizing the details in the next co

Re: [lldb-dev] [Release-testers] 13.0.0-rc3 has been tagged

On 14 Sep 2021, at 06:40, Tom Stellard via Release-testers wrote: > > I've tagged 13.0.0-rc3. This will likely be the last rc unless there are > critical bugs that are found. Please test the release and report results. For 13.0.0 rc3, I have built and tested on both FreeBSD 12 and 13. No addi

Re: [lldb-dev] [llvm-dev] 13.0.0-rc3 has been tagged

On 9/17/21 10:29 AM, Sedat Dilek wrote: @Tom Stellard Shall I open a bug-report to cherry-pick...? commit 454f69bcc17e6451c926a2e7b708e900fc8fdcb8 "[PATCH] [LLD] Add required `ppc` target to the test cases. NFC") If yes - Can you point me to the LLVM release/13.x meta bug number? Yes,that w

Re: [lldb-dev] [Release-testers] 13.0.0-rc3 has been tagged

Hi, Uploaded armv7 and aarch64 binaries: beadc6b6fab35a46b35f2053b62c8d7c2bcf0b549a789b8ee690fa86fff679a0 clang+llvm-13.0.0-rc3-aarch64-linux-gnu.tar.xz 9ebc21710d94e2a68951295c8df39d952409e125122b97ca77f819565a5afcf3 clang+llvm-13.0.0-rc3-armv7a-linux-gnueabihf.tar.xz No new failures on aarch6

[lldb-dev] [Bug 51875] New: SymbolFile/NativePDB/stack_unwinding01.cpp, SymbolFile/PDB/ast-restore.test fail on Windows due to Assertion failed: Access != AS_none && "Access specifier is AS_none insid

https://bugs.llvm.org/show_bug.cgi?id=51875 Bug ID: 51875 Summary: SymbolFile/NativePDB/stack_unwinding01.cpp, SymbolFile/PDB/ast-restore.test fail on Windows due to Assertion failed: Access != AS_none && "Access sp

[lldb-dev] Reminder: Put release-13.0.0 in the 'Blocks' field of bugs you want fixed in the 13.0.0 release

Hi, Please put release-13.0.0 in the Blocks field of bugs you want to fix in the 13.0.0 release. This is only way for me to track which bugs people want fixed. Thanks, Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-b

Re: [lldb-dev] [Release-testers] 13.0.0-rc3 has been tagged

On Mon, 2021-09-13 at 21:40 -0700, Tom Stellard via Release-testers wrote: > Hi, > > I've tagged 13.0.0-rc3. This will likely be the last rc unless there are > critical bugs that are found. Please test the release and report results. > There's one regression in compiler-rt compared to rc2: ht

[lldb-dev] 13.0.0-rc3 has been tagged

Hi, I've tagged 13.0.0-rc3. This will likely be the last rc unless there are critical bugs that are found. Please test the release and report results. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/list

[lldb-dev] [Bug 51833] New: TestGuiBasicDebug.py is flaky - lack of process event synchronization ?

https://bugs.llvm.org/show_bug.cgi?id=51833 Bug ID: 51833 Summary: TestGuiBasicDebug.py is flaky - lack of process event synchronization ? Product: lldb Version: unspecified Hardware: All OS: All

[lldb-dev] [Bug 51832] New: lldb/jit not working Windows

https://bugs.llvm.org/show_bug.cgi?id=51832 Bug ID: 51832 Summary: lldb/jit not working Windows Product: lldb Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: release blocker

[lldb-dev] [Bug 51805] Cherry-pick 8901f8beea3a70f92be8c0b80313260502f03727 into 13.x branch

https://bugs.llvm.org/show_bug.cgi?id=51805 Omair Javaid changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[lldb-dev] [Bug 51818] New: lldb crashes with relatively simple gcc debug info

https://bugs.llvm.org/show_bug.cgi?id=51818 Bug ID: 51818 Summary: lldb crashes with relatively simple gcc debug info Product: lldb Version: unspecified Hardware: All OS: All Status: NEW Severity: normal

[lldb-dev] [Bug 51805] New: Cherry-pick 8901f8beea3a70f92be8c0b80313260502f03727 into 13.x branch

https://bugs.llvm.org/show_bug.cgi?id=51805 Bug ID: 51805 Summary: Cherry-pick 8901f8beea3a70f92be8c0b80313260502f03727 into 13.x branch Product: lldb Version: unspecified Hardware: PC OS: Linux

[lldb-dev] Release Update: 13.0.0-rc3 delayed. Fix deadline extended to Friday

Hi, There were a large volume of bugs that came in over the last few days, so I'm going to delay 13.0.0-rc3 until Monday so there is more time to fix them. This also means that you now have until Friday to submit fixes for the release/13.x branch. -Tom _

[lldb-dev] 2021 LLVM Developers' Meeting - Call for Talk Proposals (Deadline Sept 20)

All developers and users of LLVM and related sub-projects are invited to present at the 2021 LLVM Developers’ Meeting ! The conference will be held November 17-19. Due to the uncertainty of COVID-19, the conference will again be online only. Full conference det

Re: [lldb-dev] [llvm-dev] [cfe-dev] 1 week until 13.0.0-rc2 release

On 9/7/21 12:41 PM, Sean McBride wrote: Pardon my ignorance, but what is "the server"? Could you share its URL so that we can download from there instead of github? The github page still does not have macOS binaries for neither the current release (12.0.1) nor the current rc (13.0.0-rc2). At

Re: [lldb-dev] Duplicate use of "sp" register name on x86 targets

On Mon, 2021-09-06 at 13:23 +0200, Pavel Labath wrote: > On 25/08/2021 21:13, Michał Górny via lldb-dev wrote: > > Hi, > > > > While working on improving gdbserver compatibility, I've noticed that > > "sp" is used twice: > > > > 1. as an alt_

Re: [lldb-dev] who is maintaining lldb-x86_64-debian

On 03/09/2021 07:00, Omair Javaid via lldb-dev wrote: Hi Jan, On Thu, 2 Sept 2021 at 17:29, Jan Kratochvil <mailto:jan.kratoch...@redhat.com>> wrote: On Thu, 02 Sep 2021 12:42:37 +0200, Raphael “Teemperor” Isemann via lldb-dev wrote: > If this is about the TestG

Re: [lldb-dev] Duplicate use of "sp" register name on x86 targets

On 25/08/2021 21:13, Michał Górny via lldb-dev wrote: Hi, While working on improving gdbserver compatibility, I've noticed that "sp" is used twice: 1. as an alt_name for esp/rsp register (giving full 32/64-bit stack pointer), 2. and as the name of sp pseudo-register (giving ES

Re: [lldb-dev] who is maintaining lldb-x86_64-debian

Hi Jan, On Thu, 2 Sept 2021 at 17:29, Jan Kratochvil wrote: > On Thu, 02 Sep 2021 12:42:37 +0200, Raphael “Teemperor” Isemann via > lldb-dev wrote: > > If this is about the TestGuiBasicDebug failures, then that test is also > > failing on other bots. I personally would vote t

Re: [lldb-dev] who is maintaining lldb-x86_64-debian

On Thu, 02 Sep 2021 12:42:37 +0200, Raphael “Teemperor” Isemann via lldb-dev wrote: > If this is about the TestGuiBasicDebug failures, then that test is also > failing on other bots. I personally would vote to disable the test as that > part of the test is flakey since its introduction (

Re: [lldb-dev] who is maintaining lldb-x86_64-debian

If this is about the TestGuiBasicDebug failures, then that test is also failing on other bots. I personally would vote to disable the test as that part of the test is flakey since its introduction (which was during this GSoC). - Raphael > On 2 Sep 2021, at 12:27, Omair Javaid via lldb-

[lldb-dev] who is maintaining lldb-x86_64-debian

Hi There have been sporadic failures due to timeouts on lldb-x86_64-debian . I don't see Pavel maintingi it now. Does anyone know who's looking after this bot? Thanks! -- Omair Javaid www.linaro.org ___ lldb-

Re: [lldb-dev] [Release-testers] 13.0.0-rc2 has been tagged

On 27 Aug 2021, at 07:20, Tom Stellard via Release-testers wrote: > > I've tagged the 13.0.0-rc2 release. Testers can begin testing and uploading > binaries. > > 13.0.0-rc3 is scheduled to be released on Sep. 7, so we'll continue to accept > bug fixes in the branch until then. For 13.0.0 rc2,

[lldb-dev] [Bug 51685] New: Crash evaluating expression

https://bugs.llvm.org/show_bug.cgi?id=51685 Bug ID: 51685 Summary: Crash evaluating expression Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: release blocker Prio

[lldb-dev] [Bug 51673] New: AArch64 debug problems on Windows

https://bugs.llvm.org/show_bug.cgi?id=51673 Bug ID: 51673 Summary: AArch64 debug problems on Windows Product: lldb Version: 10.0 Hardware: Other OS: Windows NT Status: NEW Severity: normal Priori

Re: [lldb-dev] [Release-testers] 13.0.0-rc2 has been tagged

Windows binaries are ready: $ sha256sum LLVM-13.0.0-rc2-win*.exe 5c91401dce31672646da86e0d4e9cd2f3ff7873dc411ca988f83eb1ba4e61553 LLVM-13.0.0-rc2-win32.exe 035cd6b1b9c7c4310364c948823f02165a205ae97be10262f3df0a45ccd4d6f0 LLVM-13.0.0-rc2-win64.exe Nothing new compared to rc1. Thanks, Hans On F

Re: [lldb-dev] [Release-testers] 13.0.0-rc2 has been tagged

Hi, Uploaded aarch64 & armv7 binaries: 8f692d75f71e89146877bab08760cda98378cc46275b2368b7887a2c605c13c4 clang+llvm-13.0.0-rc2-aarch64-linux-gnu.tar.xz 32148e4790ca2706d19eea7255edd0f99a97a647971cfa05f1b71eecadd7a3ac clang+llvm-13.0.0-rc2-armv7a-linux-gnueabihf.tar.xz Everything looks the same a

Re: [lldb-dev] [Release-testers] 13.0.0-rc2 has been tagged

On Thu, 2021-08-26 at 22:20 -0700, Tom Stellard via Release-testers wrote: > Hi, > > I've tagged the 13.0.0-rc2 release. Testers can begin testing and uploading > binaries. > No new bugs on my end since -rc1. To be more precise: - orclazy non-amd64 test skip still needs backporting: https:

[lldb-dev] 13.0.0-rc2 has been tagged

Hi, I've tagged the 13.0.0-rc2 release. Testers can begin testing and uploading binaries. 13.0.0-rc3 is scheduled to be released on Sep. 7, so we'll continue to accept bug fixes in the branch until then. -Tom ___ lldb-dev mailing list lldb-dev@lists

[lldb-dev] Duplicate use of "sp" register name on x86 targets

Hi, While working on improving gdbserver compatibility, I've noticed that "sp" is used twice: 1. as an alt_name for esp/rsp register (giving full 32/64-bit stack pointer), 2. and as the name of sp pseudo-register (giving ESP/RSP truncated to 16 bits). FWICS the current lookup logic (at least fo

[lldb-dev] 13.0.1-rc2 release update

Hi, There have been some buildbot failures in the release/13.x branch, so I'm going to delay -rc2 until Thursday to investigate. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 51533] [lldb] Merge 5033f0793fe6 and cf521e78dfd2 into 13.0.0

https://bugs.llvm.org/show_bug.cgi?id=51533 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)|5033f0793fe6 cf521e78df

[lldb-dev] [Bug 51533] New: [lldb] Merge 5033f0793fe6 and cf521e78dfd2 into 13.0.0

https://bugs.llvm.org/show_bug.cgi?id=51533 Bug ID: 51533 Summary: [lldb] Merge 5033f0793fe6 and cf521e78dfd2 into 13.0.0 Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity: norma

[lldb-dev] [Bug 51532] LLDB crash when breakpoint in swift file

https://bugs.llvm.org/show_bug.cgi?id=51532 Raphael Isemann changed: What|Removed |Added CC||teempe...@gmail.com Status|NEW

[lldb-dev] [Bug 51532] New: LLDB crash when breakpoint in swift file

https://bugs.llvm.org/show_bug.cgi?id=51532 Bug ID: 51532 Summary: LLDB crash when breakpoint in swift file Product: lldb Version: 12.0 Hardware: Macintosh OS: MacOS X Status: NEW Severity: normal

[lldb-dev] 1 week until 13.0.0-rc2 release

Hi, There is only 1 week until the 13.0.0-rc2 release. If you have fixes you want to get into the release please file a bug and put release-13.0.0 in the 'blocks' field. The current plan is to accept fixes until 13.0.0-rc3, which is planned for 2 weeks after 13.0.0-rc2, but the earlier we get

Re: [lldb-dev] [Release-testers] 13.0.0-rc1 has been tagged

On 3 Aug 2021, at 09:20, Tom Stellard via Release-testers wrote: > > I've tagged the 13.0.0-rc1 release. Testers, please test and upload binaries. For 13.0.0 rc1, I have built and tested on both FreeBSD 12 and 13. I used 6 patches, which are attached. (Most of these are already merged for the

[lldb-dev] [Bug 51467] New: LLDB "image list" accumulates duplicate loader+vdso images on restart

https://bugs.llvm.org/show_bug.cgi?id=51467 Bug ID: 51467 Summary: LLDB "image list" accumulates duplicate loader+vdso images on restart Product: lldb Version: unspecified Hardware: PC OS: Linux

[lldb-dev] [Bug 51466] New: LLDB can't find function containing a PC from musl libc.so

https://bugs.llvm.org/show_bug.cgi?id=51466 Bug ID: 51466 Summary: LLDB can't find function containing a PC from musl libc.so Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW

[lldb-dev] [Bug 51459] New: 'process launch -s' does not work correctly over remote lldb-server

https://bugs.llvm.org/show_bug.cgi?id=51459 Bug ID: 51459 Summary: 'process launch -s' does not work correctly over remote lldb-server Product: lldb Version: unspecified Hardware: PC OS: Linux St

[lldb-dev] [Bug 51458] New: 'process launch -s' uses gdb-remote connection only if target was created before connecting

https://bugs.llvm.org/show_bug.cgi?id=51458 Bug ID: 51458 Summary: 'process launch -s' uses gdb-remote connection only if target was created before connecting Product: lldb Version: unspecified Hardware: PC

[lldb-dev] [Bug 51451] LLDB AArch64 SVE register context fails to restore after JITTed expression eval

https://bugs.llvm.org/show_bug.cgi?id=51451 Omair Javaid changed: What|Removed |Added Status|NEW |CONFIRMED Assignee|lldb-dev@lists.llvm

[lldb-dev] [Bug 51451] New: LLDB AArch64 SVE register context fails to restore after JITTed expression eval

https://bugs.llvm.org/show_bug.cgi?id=51451 Bug ID: 51451 Summary: LLDB AArch64 SVE register context fails to restore after JITTed expression eval Product: lldb Version: 12.0 Hardware: PC OS: Linux

[lldb-dev] [Bug 51446] New: LLDB import std module tests crash with segmentation fault

https://bugs.llvm.org/show_bug.cgi?id=51446 Bug ID: 51446 Summary: LLDB import std module tests crash with segmentation fault Product: lldb Version: 12.0 Hardware: PC OS: Linux Status: NEW

[lldb-dev] [Bug 51423] Please backport 614c7d03877fd99c2de47429b15be3f00306a3bd (LLVM_LIT_ARGS override) to 13.x

https://bugs.llvm.org/show_bug.cgi?id=51423 Tom Stellard changed: What|Removed |Added Fixed By Commit(s)|614c7d03877fd99c2de47429b15 |614c7d03877fd99c2de47429b15 |b

[lldb-dev] [Bug 51418] Please backport 15cacab73f7e36d9dca4a5516ccb360b67bf2dbc (skip test if LD_PRELOAD) to 13.x

https://bugs.llvm.org/show_bug.cgi?id=51418 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)|15cacab73f7e36d9dca4a55

[lldb-dev] [Bug 51433] New: crash for "x86_64-w64-windows-gnu" because of architecture triple mismatch - solution proposition

https://bugs.llvm.org/show_bug.cgi?id=51433 Bug ID: 51433 Summary: crash for "x86_64-w64-windows-gnu" because of architecture triple mismatch - solution proposition Product: lldb Version: 12.0 Hardware: PC

[lldb-dev] [Bug 51423] New: Please backport 614c7d03877fd99c2de47429b15be3f00306a3bd (LLVM_LIT_ARGS override) to 13.x

https://bugs.llvm.org/show_bug.cgi?id=51423 Bug ID: 51423 Summary: Please backport 614c7d03877fd99c2de47429b15be3f00306a3bd (LLVM_LIT_ARGS override) to 13.x Product: lldb Version: unspecified Hardware: P

[lldb-dev] [Bug 51418] New: Please backport 15cacab73f7e36d9dca4a5516ccb360b67bf2dbc (skip test if LD_PRELOAD) to 13.x

https://bugs.llvm.org/show_bug.cgi?id=51418 Bug ID: 51418 Summary: Please backport 15cacab73f7e36d9dca4a5516ccb360b67bf2dbc (skip test if LD_PRELOAD) to 13.x Product: lldb Version: unspecified Hardware:

Re: [lldb-dev] [llvm-dev] 13.0.0-rc1 has been tagged

auto result = m_plans_list.find(tid); > if (result == m_plans_list.end()) > return false; > result->second.ThreadDestroyed(nullptr); > m_plans_list.erase(result); > return true; > } > > But the iterator of a map shouldn't require a copy

Re: [lldb-dev] [llvm-dev] 13.0.0-rc1 has been tagged

if (result == m_plans_list.end()) > return false; > result->second.ThreadDestroyed(nullptr); > m_plans_list.erase(result); > return true; > } > > But the iterator of a map shouldn't require a copy of the value, that > doesn't make sense. > &

Re: [lldb-dev] [llvm-dev] 13.0.0-rc1 has been tagged

iterator of a map shouldn't require a copy of the value, that doesn't make sense. Other than that, I can't see anything funny here. Is this something triggered by -pedantic? Jim > On Aug 4, 2021, at 4:22 PM, Vadim Chugunov via lldb-dev > wrote: > > Not sure if

Re: [lldb-dev] [llvm-dev] 13.0.0-rc1 has been tagged

Not sure if this is a supported configuration, but I am hitting this error when compiling on Ubuntu 16.04 with clang 12: FAILED: /usr/local/bin/clang++ -DGTEST_HAS_RTTI=0 -DHAVE_ROUND -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Itools/lldb/source/Plugins/A

[lldb-dev] [Bug 51280] Backport lldb AArch64 memory tagging commands changes to 13.x branch

https://bugs.llvm.org/show_bug.cgi?id=51280 David Spickett changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[lldb-dev] 13.0.0-rc1 has been tagged

Hi, I've tagged the 13.0.0-rc1 release. Testers, please test and upload binaries. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 51299] New: crash when auto-completion is triggered

https://bugs.llvm.org/show_bug.cgi?id=51299 Bug ID: 51299 Summary: crash when auto-completion is triggered Product: lldb Version: 12.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority

Re: [lldb-dev] [Release-testers] 13.0.0-rc1 pushed out to Monday

On Thu, 2021-07-29 at 23:00 -0700, Tom Stellard via Release-testers wrote: > I'm going to give the release/13.x branch a few more days to > stabilize, so I plan on tagging 13.0.0-rc1 on Monday now > instead of Friday. > I must've missed the announcement of the branch split. I suppose this is my

[lldb-dev] [Bug 51280] New: Backport lldb AArch64 memory tagging commands changes to 13.x branch

https://bugs.llvm.org/show_bug.cgi?id=51280 Bug ID: 51280 Summary: Backport lldb AArch64 memory tagging commands changes to 13.x branch Product: lldb Version: unspecified Hardware: PC OS: Linux S

[lldb-dev] 13.0.0-rc1 pushed out to Monday

Hi, I'm going to give the release/13.x branch a few more days to stabilize, so I plan on tagging 13.0.0-rc1 on Monday now instead of Friday. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-de

[lldb-dev] [Bug 51274] New: print object reference displays no members, yet there are

https://bugs.llvm.org/show_bug.cgi?id=51274 Bug ID: 51274 Summary: print object reference displays no members, yet there are Product: lldb Version: unspecified Hardware: PC OS: Windows NT Status:

Re: [lldb-dev] [RFC] Improving protocol-level compatibility between LLDB and GDB

On Mon, 2021-04-19 at 09:59 +0200, Michał Górny wrote: > I'm considering running some effort to improve protocol-level > compatibility between LLDB and GDB. I'd like to hear if there's > interest in such patches being accepted into LLDB. > > My goal would be to make it possible to use LLDB to con

[lldb-dev] release/13.x branch has been created

Hi, I've created release/13.x branch. We will wait a few days to make sure the branch is stable and then 13.0.0-rc1 will be released on Friday. If you have patches you want to backport to the release/13.x branch you can email me or file a bug that blocks the release-13.0.0 metabug[1]. In addit

[lldb-dev] Reminder: release/13.x branch will be created on Tuesday

Hi, Just a reminder that the release/13.x branch will be created on Tuesday. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 51148] New: Crash upon trying to display object member.

https://bugs.llvm.org/show_bug.cgi?id=51148 Bug ID: 51148 Summary: Crash upon trying to display object member. Product: lldb Version: 12.0 Hardware: Macintosh OS: MacOS X Status: NEW Severity: normal

Re: [lldb-dev] Should MyType's synthetic provider be instantiated for MyType* and MyType** ?

> On Jul 19, 2021, at 6:24 PM, Vadim Chugunov wrote: > > > > On Mon, Jul 19, 2021 at 6:02 PM Jim Ingham wrote: > You can control whether you want data-formatters on "class Foo" to also match > "class Foo *" and "class Foo &" using the --skip-pointers and > --skip-references options respect

Re: [lldb-dev] Should MyType's synthetic provider be instantiated for MyType* and MyType** ?

On Mon, Jul 19, 2021 at 6:02 PM Jim Ingham wrote: > You can control whether you want data-formatters on "class Foo" to also > match "class Foo *" and "class Foo &" using the --skip-pointers and > --skip-references options respectively. > So this part is clearly is by design. > > As for what the f

Re: [lldb-dev] Should MyType's synthetic provider be instantiated for MyType* and MyType** ?

other people's uses of it. Jim > On Jul 19, 2021, at 5:12 PM, Vadim Chugunov via lldb-dev > wrote: > > Hi, > I am observing that if I bind a synthetic provider to MyType, it will also be > instantiated for MyType*, MyType**, etc, and the object passed into the >

[lldb-dev] Should MyType's synthetic provider be instantiated for MyType* and MyType** ?

Hi, I am observing that if I bind a synthetic provider to MyType, it will also be instantiated for MyType*, MyType**, etc, and the object passed into the constructor will be *of the pointer type*.I'd have expected the synthetic to either not be instantiated for pointers, or to be constructed on

Re: [lldb-dev] proposed change to remove conditional WCHAR support in libedit wrapper

l 2021 10:51:34 +0200, Neal Sidhwaney via lldb-dev wrote: >> Anyone else think this could be useful? Or, conversely, does anyone see >> something that I missed that requires the conditional compilation to remain >> in? > > Oldest platform Red Hat builds LLDB on is RHEL-7

Re: [lldb-dev] proposed change to remove conditional WCHAR support in libedit wrapper

On Sun, 11 Jul 2021 14:49:25 +0200, Raphael “Teemperor” Isemann via lldb-dev wrote: > LLDB also provides a custom callback for libedit to read characters from the > command line (which mariadb probably doesn’t), so maybe we implemented that > incorrectly. Missing setlocale(), fi

Re: [lldb-dev] proposed change to remove conditional WCHAR support in libedit wrapper

Maybe mariadb is not using libedit in emacs mode? LLDB also provides a custom callback for libedit to read characters from the command line (which mariadb probably doesn’t), so maybe we implemented that incorrectly. - Raphael > On 11 Jul 2021, at 13:45, Jan Kratochvil wrote: > > On Sun, 11 J

Re: [lldb-dev] proposed change to remove conditional WCHAR support in libedit wrapper

On Sun, 11 Jul 2021 13:07:26 +0200, Raphael “Teemperor” Isemann wrote: > What libedit version/port is Fedora using? > [1] https://thrysoee.dk/editline/ Source RPM : libedit-3.1-37.20210522cvs.fc34.src.rpm URL : https://www.thrysoee.dk/editline/ > I think the usual Linux port[1] is suffe

Re: [lldb-dev] proposed change to remove conditional WCHAR support in libedit wrapper

ust echo’d as their escaped code point I have not figured out yet. [1] https://thrysoee.dk/editline/ > On 11 Jul 2021, at 11:28, Jan Kratochvil via lldb-dev > wrote: > > On Sun, 11 Jul 2021 11:11:02 +0200, Jan Kratochvil via lldb-dev wrote: >> OTOH the wide character does no

Re: [lldb-dev] proposed change to remove conditional WCHAR support in libedit wrapper

On Sun, 11 Jul 2021 11:11:02 +0200, Jan Kratochvil via lldb-dev wrote: > OTOH the wide character does not work there and even not on Fedora 34 x86_64: > typing: žščř > (lldb) \U+017E\U+0161\U+010D\U+0159 > error: 'žščř' is not a valid command. > typing: áéíóůúý > (lldb)

Re: [lldb-dev] proposed change to remove conditional WCHAR support in libedit wrapper

On Sat, 10 Jul 2021 10:51:34 +0200, Neal Sidhwaney via lldb-dev wrote: > Anyone else think this could be useful? Or, conversely, does anyone see > something that I missed that requires the conditional compilation to remain > in? Oldest platform Red Hat builds LLDB on is RHEL-7 (and i

[lldb-dev] [Bug 51048] New: x86 build failed on lldb 11

https://bugs.llvm.org/show_bug.cgi?id=51048 Bug ID: 51048 Summary: x86 build failed on lldb 11 Product: lldb Version: 11.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P

[lldb-dev] [Bug 51046] New: Empty strings removed from target's argument list

https://bugs.llvm.org/show_bug.cgi?id=51046 Bug ID: 51046 Summary: Empty strings removed from target's argument list Product: lldb Version: 10.0 Hardware: PC OS: Linux Status: NEW Severity: normal

[lldb-dev] proposed change to remove conditional WCHAR support in libedit wrapper

Hello, I was thinking of removing the conditional compilation to use libedit’s WCHAR support on non-Windows platforms. The conditional preprocessor logic is definitely the correct way to support both wide & narrow character APIs, but editline has enabled the wide API’s by default for some time

[lldb-dev] [Bug 51031] New: MapImported: Assertion `(Pos == ImportedDecls.end() || Pos->second == To) && "Try to import an already imported Decl"' failed.

https://bugs.llvm.org/show_bug.cgi?id=51031 Bug ID: 51031 Summary: MapImported: Assertion `(Pos == ImportedDecls.end() || Pos->second == To) && "Try to import an already imported Decl"' failed. Product: lldb Versi

[lldb-dev] [Bug 51015] New: Crash when showing the value of variables

https://bugs.llvm.org/show_bug.cgi?id=51015 Bug ID: 51015 Summary: Crash when showing the value of variables Product: lldb Version: unspecified Hardware: Macintosh OS: MacOS X Status: NEW Severity: normal

Re: [lldb-dev] [llvm-dev] RFC: Update LLVM_VERSION_SUFFIX CMake variable for release candidates

On 7/1/21 2:06 PM, Harald van Dijk wrote: On 01/07/2021 20:45, Tom Stellard wrote: On 7/1/21 9:18 AM, Harald van Dijk wrote: On 29/06/2021 18:39, Tom Stellard via llvm-dev wrote: Hi, I would like to propose that we start using the LLVM_VERSION_SUFFIX CMake variable for release candidates.  Fo

Re: [lldb-dev] [Release-testers] 12.0.1-rc4 release has been tagged

On Fri, 2021-07-02 at 13:59 -0700, Tom Stellard via Release-testers wrote: > Hi, > > I've tagged the 12.0.1-rc4 release. This will hopefully be the last release > candidate. Please test and upload binaries. > This mostly looks good on amd64 & x86, except that: 1. Three compiler-rt tests fail

Re: [lldb-dev] [Release-testers] 12.0.1-rc4 release has been tagged

On 2 Jul 2021, at 22:59, Tom Stellard via Release-testers wrote: > > I've tagged the 12.0.1-rc4 release. This will hopefully be the last release > candidate. Please test and upload binaries. For 12.0.1 rc4, I have built and tested on both FreeBSD 11 and 12. No additional patches were needed.

[lldb-dev] 12.0.1-rc4 release has been tagged

Hi, I've tagged the 12.0.1-rc4 release. This will hopefully be the last release candidate. Please test and upload binaries. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 50958] New: Crash when kernel debugging OS X after hitting breakpoint several times

https://bugs.llvm.org/show_bug.cgi?id=50958 Bug ID: 50958 Summary: Crash when kernel debugging OS X after hitting breakpoint several times Product: lldb Version: 12.0 Hardware: PC OS: MacOS X Sta

Re: [lldb-dev] [llvm-dev] RFC: Update LLVM_VERSION_SUFFIX CMake variable for release candidates

On 7/1/21 9:18 AM, Harald van Dijk wrote: On 29/06/2021 18:39, Tom Stellard via llvm-dev wrote: Hi, I would like to propose that we start using the LLVM_VERSION_SUFFIX CMake variable for release candidates.  For example: after the release/13.x branch is created, instead of changing LLVM_VERSION

Re: [lldb-dev] [cfe-dev] RFC: Update LLVM_VERSION_SUFFIX CMake variable for release candidates

On 7/1/21 8:26 AM, Ben Boeckel wrote: On Tue, Jun 29, 2021 at 10:39:01 -0700, Tom Stellard via cfe-dev wrote: I would like to propose that we start using the LLVM_VERSION_SUFFIX CMake variable for release candidates. For example: after the release/13.x branch is created, instead of changing LLV

[lldb-dev] [Bug 50948] New: LLDB not clearing EXC_BAD_ACCESS exception after `thread return` (on MacOS)?

https://bugs.llvm.org/show_bug.cgi?id=50948 Bug ID: 50948 Summary: LLDB not clearing EXC_BAD_ACCESS exception after `thread return` (on MacOS)? Product: lldb Version: unspecified Hardware: PC OS: MacOS X

[lldb-dev] [Bug 50936] New: lldb step over glibc dlopen fails (__GI__dl_catch_exception or runs away)

https://bugs.llvm.org/show_bug.cgi?id=50936 Bug ID: 50936 Summary: lldb step over glibc dlopen fails (__GI__dl_catch_exception or runs away) Product: lldb Version: 12.0 Hardware: PC OS: Linux Sta

[lldb-dev] [Bug 50935] New: lldb step over failed in musl dyn exe (Could not create return address breakpoint)

https://bugs.llvm.org/show_bug.cgi?id=50935 Bug ID: 50935 Summary: lldb step over failed in musl dyn exe (Could not create return address breakpoint) Product: lldb Version: 12.0 Hardware: PC OS: Linux

[lldb-dev] RFC: Update LLVM_VERSION_SUFFIX CMake variable for release candidates

Hi, I would like to propose that we start using the LLVM_VERSION_SUFFIX CMake variable for release candidates. For example: after the release/13.x branch is created, instead of changing LLVM_VERSION_SUFFIX from "git" to "", we would change it to "rc1", then after the 13.0.0-rc1 release is tagged

Re: [lldb-dev] [cfe-dev] 12.0.1-rc3 has been tagged

On 26 Jun 2021, at 07:49, Tom Stellard via cfe-dev wrote: > > I've tagged the 12.0.1-rc3 release. Testers please test and upload binaries. For 12.0.1 rc3, I have built and tested on both FreeBSD 11 and 12. No additional patches were needed. Main results on amd64-freebsd11: Unsupported

Re: [lldb-dev] [cfe-dev] 12.0.1-rc3 has been tagged

On Sat, Jun 26, 2021 at 7:50 AM Tom Stellard via cfe-dev < cfe-...@lists.llvm.org> wrote: > Hi, > > I've tagged the 12.0.1-rc3 release. Testers please test and upload > binaries. > Windows is ready: $ sha256sum LLVM-12.0.1-rc3-win*.exe 51c2f6312646a98f37d916d135bafcfcdddaf5bc59b2f7dbb487532817

Re: [lldb-dev] [Release-testers] Release 12.0.1-rc2 tagged + extended deadline for requesting backports

On 17 Jun 2021, at 08:53, Tom Stellard via Release-testers wrote: > > I've tagged the 12.0.1-rc2 release, so testers may begin testing and uploading > binaries. For 12.0.1 rc2, I have built and tested on both FreeBSD 11 and 12. No additional patches were needed. Main results on amd64-freebsd1

[lldb-dev] 12.0.1-rc3 has been tagged

Hi, I've tagged the 12.0.1-rc3 release. Testers please test and upload binaries. -Tom ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 50861] New: libstdc++ tests fail with GCC as the test compiler

https://bugs.llvm.org/show_bug.cgi?id=50861 Bug ID: 50861 Summary: libstdc++ tests fail with GCC as the test compiler Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal

<    1   2   3   4   5   6   7   8   9   10   >