Re: [lldb-dev] [llvm-dev] HTTP library in LLVM

On Mon, Aug 31, 2020 at 4:38 PM Petr Hosek via llvm-dev < llvm-...@lists.llvm.org> wrote: > There are several options, I've looked at couple of them and the one I > like the most so far is https://github.com/yhirose/cpp-httplib for a few > reasons: > > * It's MIT licensed. > * It supports Linux, m

[lldb-dev] [RFC] Segmented Address Space Support in LLDB

We want to support segmented address spaces in LLDB. Currently, all of LLDB’s external API, command line interface, and internals assume that an address in memory can be addressed unambiguously as an addr_t (aka uint64_t). To support a segmented address space we’d need to extend addr_t with a discr

Re: [lldb-dev] Deleting lldb/utils/test/

Last time I looked at these nothing seemed relevant (anymore) to me either. I'm in favor of getting rid of the directory. On Tue, Oct 27, 2020 at 10:26 AM Vedant Kumar via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Hi, > > I'm considering deleting the lldb/utils/test/ directory as a cleanup. Do

Re: [lldb-dev] [RFC] Segmented Address Space Support in LLDB

be worried about over-generalizing specialized code which can >>> afford to work with plain addresses, and where the added address space >>> would be a nuisance (or a source of bugs). E.g. ELF has no notion of address >>> space, so I don't think I'd find it hel

Re: [lldb-dev] [RFC] Moving away from epydoc for the LLDB SB API documentation

Another issue with epydoc is that it currently doesn't list properties. The checked-in documentation from the old days had them, but I never got epydoc to generate them (and to be fair I never really tried). Instead I looked at alternatives as well. The main issue I found is that it's easy to trick

Re: [lldb-dev] Updating or removing lldb's copy of unittest2

Hey David, On Thu, Jan 28, 2021 at 2:46 AM David Spickett via lldb-dev < lldb-dev@lists.llvm.org> wrote: > I came across a minor bug writing some lldb-server tests where single > line diffs weren't handled correctly by unittest2. Turns out they are > in the latest version but the third_party/ ver

Re: [lldb-dev] Removing linux mips support

+1 This all sounds in line with the expectations we've laid out on the mailing list in the past for platform/language support. On Tue, Mar 9, 2021 at 12:24 AM Pavel Labath via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Hi all, > > I propose to remove support for linux mips debugging. This basi

[lldb-dev] LLDB Reproducers

Hey everyone, Over the course of the past year, I've come to the conclusion that the reproducers still require a non-trivial amount of investment to reach production quality. Unfortunately, I don't have the bandwidth to make that happen. Reproducers are inherently all-or-nothing: they either fait

Re: [lldb-dev] [llvm-dev] [RFC] Building LLVM-Debuginfod

+lldb-dev On Mon, Oct 4, 2021 at 11:01 PM Petr Hosek via llvm-dev < llvm-...@lists.llvm.org> wrote: > Two major factors are compatibility with a broad range of platforms (our > toolchain is already being used by developers on Linux, macOS, Windows) and > permissive license (our goal is to provide

Re: [lldb-dev] Is GetLogIf**All**CategoriesSet useful?

> On Jan 19, 2022, at 10:25 AM, Jim Ingham wrote: > > > >> On Jan 19, 2022, at 6:40 AM, Pavel Labath wrote: >> >> Hi all, >> >> In case you haven't noticed, I'd like to draw your attention to the >> in-flight patches (https://reviews.llvm.org/D117382, >> https://reviews.llvm.org/D117490)

<    1   2