[lldb-dev] [Bug 43625] DataExtractor::GetCStr may access extra byte out of bound when working with non-zero terminated string

https://bugs.llvm.org/show_bug.cgi?id=43625 Raphael Isemann changed: What|Removed |Added Assignee|lldb-dev@lists.llvm.org |teempe...@gmail.com Status|NEW

Re: [lldb-dev] [llvm-dev] [cfe-dev] RFC: End-to-end testing

On Thu, 10 Oct 2019 at 10:56, Florian Hahn wrote: > Have you considered alternatives to checking the assembly for ensuring > vectorization or other transformations? For example, instead of checking the > assembly, we could check LLVM’s statistics or optimization remarks. If you > want to

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: End-to-end testing

David Greene, will you be at the LLVM Dev Meeting? If so, could you sign up for a Round Table session on this topic? Obviously lots to discuss and concerns to be addressed. In particular I think there are two broad categories of tests that would have to be segregated just by the nature of their

Re: [lldb-dev] [Openmp-dev] GitHub Migration Schedule and Plans

On 10/09/2019 10:16 PM, Tom Stellard via Openmp-dev wrote: > Hi, > > We're less than 2 weeks away from the developer meeting, so I wanted to > give an update on the GitHub migration and what's (hopefully) going to > happen during the developer meeting. > > Everyone who has added their

Re: [lldb-dev] [llvm-dev] [cfe-dev] RFC: End-to-end testing

> -Original Message- > From: llvm-dev On Behalf Of David Greene > via llvm-dev > Sent: Wednesday, October 09, 2019 9:17 PM > To: Mehdi AMINI > Cc: llvm-...@lists.llvm.org; cfe-...@lists.llvm.org; openmp- > d...@lists.llvm.org; lldb-dev@lists.llvm.org > Subject: Re: [llvm-dev] [cfe-dev]

Re: [lldb-dev] test setup for windows -- makefiles

I'm not sure this is entirely up to date, but I'd start here, especially the Software section: https://llvm.org/docs/GettingStartedVS.html We get most of those unix-y tools on Windows via GnuWin32. For LLDB development, you almost certainly want a Python 3 rather than the recommended 2.7.

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: End-to-end testing

Florian Hahn via cfe-dev writes: > Have you considered alternatives to checking the assembly for ensuring > vectorization or other transformations? For example, instead of > checking the assembly, we could check LLVM’s statistics or > optimization remarks. Yes, absolutely. We have tests that

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: End-to-end testing

On Thu, 10 Oct 2019 at 22:26, David Greene wrote: > That would be a shame. Where is test-suite run right now? Are there > bots? How are regressions reported? There is no shame in making the test-suite better. We do have bots running them in full CI for multiple targets, yes. Regressions are

[lldb-dev] LLDB finish_swig and Python module installation broken for multi-configuration generators

Starting in r372835 (Fix installing Python modules on systems using /usr/lib), the finish_swig and installation steps using multi-configuration generators (like Visual Studio or XCode) are broken. The problem is the symlink and install steps look for liblldb and site-packages the wrong

Re: [lldb-dev] [llvm-dev] [cfe-dev] GitHub Migration Schedule and Plans

On 10/10/2019 03:50 PM, Mehdi AMINI wrote: > > > On Thu, Oct 10, 2019 at 1:14 PM Jordan Rupprecht > wrote: > > > > On Thu, Oct 10, 2019 at 12:29 PM Tom Stellard via llvm-dev > mailto:llvm-...@lists.llvm.org>> wrote: > > On 10/10/2019 11:40 AM, Mehdi

[lldb-dev] does vFile:Open actually work?

The comments in File.h say: // NB this enum is used in the lldb platform gdb-remote packet // vFile:open: and existing values cannot be modified. enum OpenOptions { eOpenOptionRead = (1u << 0), // Open file for reading eOpenOptionWrite = (1u << 1), // Open file for writing

Re: [lldb-dev] [llvm-dev] [cfe-dev] RFC: End-to-end testing

Florian Hahn via llvm-dev writes: >> - Performance varies from implementation to implementation. It is >> difficult to keep tests up-to-date for all possible targets and >> subtargets. > > Could you expand a bit more what you mean here? Are you concerned > about having to run the performance

Re: [lldb-dev] [cfe-dev] GitHub Migration Schedule and Plans

On Thu, 10 Oct 2019, Mehdi AMINI wrote: On Thu, Oct 10, 2019 at 12:02 PM Martin Storsjö wrote: On Thu, 10 Oct 2019, Tom Stellard via cfe-dev wrote: > On 10/09/2019 11:05 PM, Mehdi AMINI wrote: >> >> >> On Wed, Oct 9, 2019 at 10:16 PM Tom Stellard via cfe-dev

Re: [lldb-dev] [cfe-dev] GitHub Migration Schedule and Plans

On 10/09/2019 11:05 PM, Mehdi AMINI wrote: > > > On Wed, Oct 9, 2019 at 10:16 PM Tom Stellard via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > Hi, > > We're less than 2 weeks away from the developer meeting, so I wanted to > give an update on the GitHub migration and

Re: [lldb-dev] [cfe-dev] GitHub Migration Schedule and Plans

On Thu, 10 Oct 2019, Tom Stellard via cfe-dev wrote: On 10/09/2019 11:05 PM, Mehdi AMINI wrote: On Wed, Oct 9, 2019 at 10:16 PM Tom Stellard via cfe-dev mailto:cfe-...@lists.llvm.org>> wrote: Hi, We're less than 2 weeks away from the developer meeting, so I wanted to give an

Re: [lldb-dev] [cfe-dev] GitHub Migration Schedule and Plans

On 10/10/2019 11:40 AM, Mehdi AMINI wrote: > > > On Thu, Oct 10, 2019 at 10:59 AM Tom Stellard > wrote: > > On 10/09/2019 11:05 PM, Mehdi AMINI wrote: > > > > > > On Wed, Oct 9, 2019 at 10:16 PM Tom Stellard via cfe-dev >

Re: [lldb-dev] [cfe-dev] [llvm-dev] RFC: End-to-end testing

Renato Golin via cfe-dev writes: > I'd recommend trying to move any e2e tests into the test-suite and > make it easier to run, and leave specific tests only in the repo (to > guarantee independence of components). That would be a shame. Where is test-suite run right now? Are there bots? How

Re: [lldb-dev] LLDB finish_swig and Python module installation broken for multi-configuration generators

Dnia October 10, 2019 11:11:20 PM UTC, Ted Woodward napisał(a): >Starting in r372835 (Fix installing Python modules on systems using >/usr/lib), the finish_swig and installation steps using >multi-configuration generators (like Visual Studio or XCode) are >broken. > >The problem is the symlink

Re: [lldb-dev] does vFile:Open actually work?

Yeah, this is a bug in lldb's implementation of vFile:open. lldb talks to lldb-server (in platform mode) so it will work with itself, but it will not interoperate with any other implementations. That's the down side to having the client and server literally built from the same sources. :)