Re: [lldb-dev] [RFC] Supporting Lua Scripting in LLDB

Python is in general a no-go for a BSD basesystem (micropython can be an exception.. but Python is so large today that we can reevaluate this statement at some point). This is why we need to either disable certain features in LLDB or split LLDB between everything without Python in the base and the

Re: [lldb-dev] issue with lldb9 and python3.5

On 30.10.2019 11:06, Pavel Labath wrote: > On 29/10/2019 21:40, Christos Zoulas wrote: >> On Oct 29,  6:54pm, pa...@labath.sk (Pavel Labath) wrote: >> -- Subject: Re: [lldb-dev] issue with lldb9 and python3.5 >> >> | On 29/10/2019 09:31, Serge Guelton via lldb-dev wrote: >> | > On Mon, Oct 28, 2019

Re: [lldb-dev] issue with lldb9 and python3.5

On 29.10.2019 21:40, Christos Zoulas wrote: > On Oct 29, 6:54pm, pa...@labath.sk (Pavel Labath) wrote: > -- Subject: Re: [lldb-dev] issue with lldb9 and python3.5 > > | On 29/10/2019 09:31, Serge Guelton via lldb-dev wrote: > | > On Mon, Oct 28, 2019 at 10:09:53AM -0700, Adrian McCarthy wrote: >

Re: [lldb-dev] [8.0.0 Release] Release schedule

On 03.12.2018 14:04, Hans Wennborg via lldb-dev wrote: > Hello everyone, > > I know 7.0.1 isn't out the door yet, and 8.0.0 isn't due for a while, > so relax :-) But I would like to get the schedule decided before folks > disappear over the holidays. > > According to the usual schedule, the branc

[lldb-dev] LLDB/NetBSD - Status June 2018

MKSANITIZER - bug detector software integration with the NetBSD userland I've finished the integration of sanitizers with the distribution build framework. A bootable and installable distribution is now available, verified with Address Sanitizer, with Undefined Behavior Sanitizer, or with both con

[lldb-dev] LLDB/NetBSD report May/2018: Coverage of signal routines in the kernel in the context of ptrace(2)

The number of ATF ptrace(2) tests cases has been significantly incremented, however there is still a substantial amount of work to be done and a number of serious bugs to be resolved. With fixes and addition of new test cases, as of today we are passing 1,206 (last month: 961) ptrace(2) tests and

[lldb-dev] Forking fixes in the context of debuggers

For the past month I've been mostly working on improving the kernel code in the ptrace(2) API. Additionally, I've prepared support for reading NetBSD/aarch64 core(5) files. A critical Problem Report kern/51630 regarding lack of PTRACE_VFORK implementation has been fixed. This means that there are

[lldb-dev] NetBSD ptrace(2) hardening status

I've spent a month on fixes and debugging issues around the tracing facilities in the kernel. Plan for the next milestone Keep working on the bug reproducible with X86 Debug Registers and switch to the remaining ptrace(2) failures. http://blog.netbsd.org/tnf/entry/struggling_to_fix_a_bohrbug

[lldb-dev] LLDB/NetBSD - Status February 2018

I've managed to unbreak the LLDB debugger as much as possible with the current kernel and hit problems with ptrace(2) that are causing issues with further work on proper NetBSD support. Meanwhile, I've upstreamed all the planned NetBSD patches to sanitizers and helped other BSDs to gain better or i

Re: [lldb-dev] [6.0.0 Release] TIme to wrap it up

On 19.02.2018 16:57, Hans Wennborg via lldb-dev wrote: > I would also like to get the release notes ready this week. If you've > been meaning to write something but didn't get around to it yet, now > is the time. > Notes regarding the X86(_64) backend: Preliminary support for Sanitizers and sibli

Re: [lldb-dev] The LLVM Sanitizers stage accomplished

considered) setting up an LLDB buildbot > that runs the LLDB test suite with all of the sanitizers turned on? > > On Thu, Feb 1, 2018 at 5:39 AM Kamil Rytarowski via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wrote: > > I've finished the

[lldb-dev] The LLVM Sanitizers stage accomplished

I've finished the interruption for LLVM Sanitizers: http://blog.netbsd.org/tnf/entry/the_llvm_sanitizers_stage_accomplished Plan for the next milestone: Keep upstreaming a pile of local compiler-rt patches. Restore the LLDB support for traced programs with a single thread. This work was spons

[lldb-dev] The LLVM Memory Sanitizer support work in progress

I've prepared a report of the past month on MSan: https://blog.netbsd.org/tnf/entry/the_llvm_memory_sanitizer_support This is work in progress and I will keep working on MSan. I can already sanitize trivial programs, but not the larger ones. Sanitizing LLDB/NetBSD with MSan is still distant. s

Re: [lldb-dev] Sanitizers update: The LLVM Thread Sanitizer has been ported to NetBSD

t the sanitizers aboard. I will be back to LLDB once I will finish MSan. On 30.11.2017 21:27, Zachary Turner wrote: > Have you been able to run lldb under any sanitizers yet? > On Thu, Nov 30, 2017 at 12:24 PM Kamil Rytarowski via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wrote: > >

[lldb-dev] Sanitizers update: The LLVM Thread Sanitizer has been ported to NetBSD

Hello, I've finished the LLVM TSan porting: https://blog.netbsd.org/tnf/entry/the_llvm_thread_sanitizer_has Next goal: Finish MSan followed by the switch to LLDB/NetBSD corrections. signature.asc Description: OpenPGP digital signature ___ lldb-dev m

[lldb-dev] One year checkpoint and Thread Sanitizer update

The past year has been started with bugfixes and the development of regression tests for ptrace(2) and related kernel features, as well as the continuation of bringing LLDB support and LLVM sanitizers (ASan + UBsan and partial TSan + Msan) to NetBSD. My plan for the next year is to finish implement

Re: [lldb-dev] EuroBSDcon2017 - The LLDB Debugger on NetBSD

On 26.09.2017 19:15, Kamil Rytarowski wrote: > Hello, > > I've uploaded my slides from the EuroBSDcon 2017 event about: > >"The LLDB Debugger on NetBSD" > > to: > >http://netbsd.org/~kamil/eurobsdcon2017.html > > There is a recording available on YouTube: > >https://youtu.be/qX0BS

[lldb-dev] EuroBSDcon2017 - The LLDB Debugger on NetBSD

Hello, I've uploaded my slides from the EuroBSDcon 2017 event about: "The LLDB Debugger on NetBSD" to: http://netbsd.org/~kamil/eurobsdcon2017.html There is a recording available on YouTube: https://youtu.be/qX0BS4P65cQ?t=16835 signature.asc Description: OpenPGP digital signature

[lldb-dev] LLVM libFuzzer and SafeStack ported to NetBSD

Hello, I've prepared a summary of the last month: http://blog.netbsd.org/tnf/entry/llvm_libfuzzer_and_safestack_ported This month I will not work on a new development and I will focus on relax and taking part in EuroBSDcon in Paris. I will speak about the LLDB porting to NetBSD. Long-term goals

Re: [lldb-dev] [llvm-dev] [5.0.0 Release] Please help fix the remaining blockers (2 days left!)

On 22.08.2017 01:36, Hans Wennborg via llvm-dev wrote: > Hello everyone, > > According to the release schedule, we're supposed to be tagging > 'final' on Wednesday. Unfortunately, I suspect we will be a little > late. > > There are currently 32 open release blockers: > https://bugs.llvm.org/bugli

Re: [lldb-dev] LLDB: Sanitizing the debugger's runtime

On 03.07.2017 18:41, Kamil Rytarowski wrote: > On 06.06.2017 17:47, Kamil Rytarowski wrote: >> Hello, >> > > Hello, > > Short update. > >> I posted the LLDB/NetBSD report for May: >> >> https://blog.netbsd.org/tnf/entry/lldb_sanitizing_the_debugger_s >> >> I'm heading now to get the LLVM sanitiz

Re: [lldb-dev] LLDB: Sanitizing the debugger's runtime

On 06.06.2017 17:47, Kamil Rytarowski wrote: > Hello, > Hello, Short update. > I posted the LLDB/NetBSD report for May: > > https://blog.netbsd.org/tnf/entry/lldb_sanitizing_the_debugger_s > > I'm heading now to get the LLVM sanitizers aboard and use them for > further development of the LLDB

[lldb-dev] LLDB: Sanitizing the debugger's runtime

Hello, I posted the LLDB/NetBSD report for May: https://blog.netbsd.org/tnf/entry/lldb_sanitizing_the_debugger_s I'm heading now to get the LLVM sanitizers aboard and use them for further development of the LLDB/NetBSD port. I need to modify the whole stack of LLVM (llvm, clang, compiler-rt, li

Re: [lldb-dev] lldb-server tests

Thank you for this work. I will add a usual requirement - please make sure that "check-lldb-unit" works in standalone builds. On 15.05.2017 16:33, Pavel Labath wrote: > Hello all, > > In case you haven't noticed it, I'd like to draw your attention to > D32930, where we're proposing a new test fr

Re: [lldb-dev] LLDB/NetBSD May

On 03.05.2017 23:10, Christos Zoulas wrote: > On May 3, 10:25pm, n...@gmx.com (Kamil Rytarowski) wrote: > | B. > | I'm still verifying single stepping of LWPs in processes with multiple > | threads. I have an impression that something is fragile there. > > Ok. Let me know when you have a reproduci

Re: [lldb-dev] LLDB/NetBSD May

On 02.05.2017 22:04, Kamil Rytarowski wrote: > > There are two bugs: > 1. kernel crashes with threads in the local copy of Process Plugin. > 2. PT_SUSPEND, PT_RESUME unreliable http://gnats.netbsd.org/51995 > > I'm working on (1.) now. > > If possible please help with (2.) as there are ATF tes

Re: [lldb-dev] LLDB/NetBSD May

On 02.05.2017 21:48, Christos Zoulas wrote: > On May 2, 9:06pm, n...@gmx.com (Kamil Rytarowski) wrote: > -- Subject: LLDB/NetBSD May > > | I put a summary of April achievements here: > | > | http://blog.netbsd.org/tnf/entry/lldb_netbsd_process_plugin_enhancements > > Thanks, that looks great. >

Re: [lldb-dev] NetBSD core(5) files for LLDB's test-suite

On 02.05.2017 16:50, Pavel Labath wrote: > Sorry it took me so long. I think it's fine to check a couple of those > in. When zipped, they will still be orders of magnitude smaller then > the windows minidump exe we are carrying around. > > For the long term though, I'd like to add the necessary su

[lldb-dev] LLDB/NetBSD May

I put a summary of April achievements here: http://blog.netbsd.org/tnf/entry/lldb_netbsd_process_plugin_enhancements The plan for the next milestone is continuing development of threads in the NetBSD Process Plugin. I will need to work more on correctness of ptrace(2) calls as new issues were det

Re: [lldb-dev] New build machine in the cluster lldb-amd64-ninja-netbsd8

rt is needed every time you update the zorg repository. > > cheers, > pl > > On 28 April 2017 at 03:40, Kamil Rytarowski wrote: >> On 24.04.2017 11:42, Pavel Labath wrote: >>> >>> >>> On 22 April 2017 at 23:57, Kamil Rytarowski via lldb-dev >>> ma

Re: [lldb-dev] New build machine in the cluster lldb-amd64-ninja-netbsd8

On 24.04.2017 11:42, Pavel Labath wrote: > > > On 22 April 2017 at 23:57, Kamil Rytarowski via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wrote: > > Hello, > > I'm in process of attaching new build machine lldb-amd64-ninja-netbsd8. > > I

Re: [lldb-dev] New build machine in the cluster lldb-amd64-ninja-netbsd8

On 24.04.2017 11:42, Pavel Labath wrote: > > > On 22 April 2017 at 23:57, Kamil Rytarowski via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wrote: > > Hello, > > I'm in process of attaching new build machine lldb-amd64-ninja-netbsd8. > > I

[lldb-dev] New build machine in the cluster lldb-amd64-ninja-netbsd8

Hello, I'm in process of attaching new build machine lldb-amd64-ninja-netbsd8. It will run prerelease of NetBSD/amd64 8.0 (as of today 7.99.70) with the GNU toolchain. Once the new one setup will be in operation, I will upgrade the old one to 7.99.70 (& retain the same name), switch the to the s

[lldb-dev] NetBSD core(5) files for LLDB's test-suite

Hello, I've prepared two sets of core(5) files with the following programs: - 1lwp_SIGSEGV (signal SIGSEGV emitted for thread) - 1lwp_busyloop (signal SIGABRT emitted for the whole process) My compiler is GCC 5.4.0 and host NetBSD/amd64 7.99.70. The first set is written with a custom startup a

Re: [lldb-dev] Patch to Attach pid successfully from different dir

Thanks, Ed Maste is the current FreeBSD maintainer. On 20.04.2017 07:36, vignesh balu wrote: > Created Review : https://reviews.llvm.org/D32271 > > Do i need to assign the reviewers ? if so please let me know how to get > reviewers list. > > -vbalu > > > On Wed, Apr 19, 2017 at 7:59 PM, Kamil

Re: [lldb-dev] Patch to Attach pid successfully from different dir

On 19.04.2017 16:15, vignesh balu via lldb-dev wrote: > Hi, > Firstly, I am new to the community, So please bear with my mistakes and > guide me to be on your wavelength. > > While using lldb we found the small bug with attaching to the running > process. > "attach" works fine when we run the lld

Re: [lldb-dev] Aprilis LLDB/NetBSD

On 04.04.2017 22:24, Kamil Rytarowski wrote: > Hello, > Hello, Short update. > I've dropped few paragraphs on the NetBSD status: > > https://blog.netbsd.org/tnf/entry/netbsd_the_first_bsd_introducing > > I'm going to focus on the following tasks till Easter holidays On time. > * watchpoint

Re: [lldb-dev] Improve performance of crc32 calculation

There is a good crc32c (assuming we want crc32c) code in DPDK (BSD-licensed). http://dpdk.org/browse/dpdk/tree/lib/librte_hash It has hardware assisted algorithm for x86 and arm64 (if hardware supports it). There is a fallback to lookup table implementation. CRC32 is definitely worth merging wit

Re: [lldb-dev] Aprilis LLDB/NetBSD

On 05.04.2017 02:21, Christos Zoulas wrote: > On Apr 5, 1:10am, n...@gmx.com (Kamil Rytarowski) wrote: > -- Subject: Re: Aprilis LLDB/NetBSD > > | Currently there is nothing planned on the base system side. All the > | enhancements are to be done on the LLDB side. > | > | Our core-dump files con

Re: [lldb-dev] Aprilis LLDB/NetBSD

On 05.04.2017 00:52, Christos Zoulas wrote: > On Apr 4, 10:24pm, n...@gmx.com (Kamil Rytarowski) wrote: > -- Subject: Aprilis LLDB/NetBSD > > | Hello, > | > | I've dropped few paragraphs on the NetBSD status: > | > | https://blog.netbsd.org/tnf/entry/netbsd_the_first_bsd_introducing > | > | I'm

[lldb-dev] Aprilis LLDB/NetBSD

Hello, I've dropped few paragraphs on the NetBSD status: https://blog.netbsd.org/tnf/entry/netbsd_the_first_bsd_introducing I'm going to focus on the following tasks till Easter holidays * watchpoints support, * floating point registers support, * enhance core(5) and make it work for multiple

Re: [lldb-dev] LLDB/NetBSD extended set of tasks

On 17.03.2017 10:48, Pavel Labath wrote: > On 16 March 2017 at 21:43, Kamil Rytarowski > >> I imagined a possible flow of ResumeAction calls like: >> [Generic/Native framework knows upfront the image of threads within >> debuggee] >> - Resume Thread 2 (PT_RESUME) >> - Suspend Thread 3 (PT_SUSPEND

Re: [lldb-dev] LLDB/NetBSD extended set of tasks

On 17.03.2017 01:37, Jim Ingham wrote: > The main consumer of thread stop reasons is the execution control > (ThreadPlans - which handle stepping & function calling - and > StopInfo::PerformAction which handles breakpoint/watchpoint hits). The only > bad effect of populating all the threads wit

Re: [lldb-dev] LLDB/NetBSD extended set of tasks

On 16.03.2017 22:59, Jim Ingham wrote: > But it looks like all the "whole process" events you are talking about are > not stop reasons but more start actions. That makes sense, but what whole > process stop events do you mean? A process can be stopped with a signal. A signal can be emitted to:

Re: [lldb-dev] LLDB/NetBSD extended set of tasks

On 16.03.2017 11:55, Pavel Labath wrote: > On 16 March 2017 at 00:43, Kamil Rytarowski wrote: >> >> TODO: >> - Fixing software breakpoints support, Fixed! 267->596 of succeeded tests out of 1200+ - please scroll for details. >> - Special Registers (Floating Point..) reading/writing, >> - Unl

Re: [lldb-dev] LLDB/NetBSD extended set of tasks

On 01.03.2017 10:13, Kamil Rytarowski wrote: > Hello, > > The contract for the LLDB port on NetBSD has been prolonged by The > NetBSD Foundation. The additional time will cover the features that were > delayed in order to address blockers that were unveiled during the work > that has been done. >

[lldb-dev] LLDB/NetBSD extended set of tasks

Hello, The contract for the LLDB port on NetBSD has been prolonged by The NetBSD Foundation. The additional time will cover the features that were delayed in order to address blockers that were unveiled during the work that has been done. I've summarized the newly finished task segment in this bl

Re: [lldb-dev] Shared Process plugin between Linux and BSD

I've published a short report for the previous milestone, with goals for the ongoing one. "The first patch-bulk upstreamed to LLDB" http://blog.netbsd.org/tnf/entry/the_first_patch_bulk_upstreamed The next one will turn to be more exciting as I plan to start with implementation of accessors f

Re: [lldb-dev] Win64 lldb build broken, llvm::call_once and _mm_mfence

On 08.02.2017 22:41, Pavel Labath wrote: > My fix was just correcting places Kamil forgot to update (or updated > over-excessively). It does not touch the root problem. > > That said, our windows bot > is building > lldb with vs2015. It doe

Re: [lldb-dev] Win64 lldb build broken, llvm::call_once and _mm_mfence

On 08.02.2017 22:14, Kamil Rytarowski wrote: > // std::call_once from libc++ is used on all Unix platforms. Other > // implementations like libstdc++ are known to have problems on NetBSD, > // OpenBSD and PowerPC. > #if defined(LLVM_ON_UNIX) && (defined(_LIBCPP_VERSION) || > \ > !(defined

Re: [lldb-dev] Win64 lldb build broken, llvm::call_once and _mm_mfence

It looks fine: diff --git a/source/Host/windows/HostInfoWindows.cpp b/source/Host/windows/HostInfoWindows.cpp index a965ec0ea..5b38e6021 100644 --- a/source/Host/windows/HostInfoWindows.cpp +++ b/source/Host/windows/HostInfoWindows.cpp @@ -18,6 +18,7 @@ #include "llvm/Support/ConvertUTF.h" #incl

Re: [lldb-dev] Shared Process plugin between Linux and BSD

Hello, For the reference in this thread, I've posted a blog entry on the NetBSD Foundation site with a summary of the interfaces we were discussing in this thread: http://blog.netbsd.org/tnf/entry/summary_of_the_preliminary_lldb This report covers the topics discussed in this E-mail thread. I'v

Re: [lldb-dev] Shared Process plugin between Linux and BSD

On 15.12.2016 16:08, Pavel Labath wrote: > On 15 December 2016 at 14:14, Kamil Rytarowski wrote: >> On 15.12.2016 14:14, Pavel Labath wrote: > > 2. PTRACE_SETSIGINFO - equivalent currently unsupported, I will need to > add support for it in ptrace(2). >>> This value is currently only u

Re: [lldb-dev] Shared Process plugin between Linux and BSD

On 15.12.2016 14:14, Pavel Labath wrote: > I am communicating with Kamil about the possibility of sharing code > between the two plugins. We plan to have a common base class for the > shared functionality between the OSs. I have asked Kamil to perform > this experiment, so we can identify which par

[lldb-dev] Shared Process plugin between Linux and BSD

Hello, I've prepared two patches to make the Linux Process Plugin buildable on NetBSD. The diff will help to transform the Linux process plugin to common code, shared between Linux and BSDs (FreeBSD, NetBSD). lldb-git: Enable Linux Process plugin on NetBSD https://wip.pkgsrc.org/cgi-bin/gitweb.

Re: [lldb-dev] [Lldb-commits] LLGS for Free/NetBSD

On 25.10.2016 01:43, Saleem Abdulrasool via lldb-dev wrote: > On Mon, Oct 24, 2016 at 11:38 AM, Ed Maste via lldb-commits > mailto:lldb-comm...@lists.llvm.org>> wrote: > > On 24 October 2016 at 06:26, Pavel Labath > wrote: > > > > It's not my place to t

Re: [lldb-dev] LLGS for Free/NetBSD (was: Re: [PATCH] D25756: FreeBSD ARM support for software single step.)

On 24.10.2016 20:38, Ed Maste wrote: > On 24 October 2016 at 06:26, Pavel Labath wrote: >> >> It's not my place to tell you how to work, but I'd recommend a >> different approach to this. If you base your work on the current >> FreeBSD in-process plugin, then when you get around to actually >> imp

Re: [lldb-dev] NetBSD buildbot new machine

New machine is up and running. There is more power and it builds the whole distribution within 35 minutes. On 04.10.2016 15:13, Kamil Rytarowski via lldb-dev wrote: > Hello, > > I'm in process of switching a machine for NetBSD buildbot. It will be > tempor

[lldb-dev] NetBSD buildbot new machine

Hello, I'm in process of switching a machine for NetBSD buildbot. It will be temporarily unavailable. signature.asc Description: OpenPGP digital signature ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo

Re: [lldb-dev] Build failure with llvm/IR/Attributes.gen?

It works now, thank you! On 03.10.2016 02:15, Chris Bieneman wrote: > This is a different missing dependency. I've committed r283081 to fix > this one and another one that I found. Hopefully that should get things > working. > > -Chris > > On Oct 2, 2016, at 5:39 AM, Kamil Rytarowski

Re: [lldb-dev] Build failure with llvm/IR/Attributes.gen?

It's still broken for NetBSD http://lab.llvm.org:8011/builders/lldb-amd64-ninja-netbsd7/builds/6775 On 30.09.2016 01:04, Chris Bieneman via lldb-dev wrote: > Hal, thanks for the heads up. I just committed a patch that should resolve > this in r282803. > > Thanks! > -Chris > >> On Sep 29, 2016,

Re: [lldb-dev] [OS X]: building lldb with cmake

On 09.09.2016 10:55, René J.V. Bertin via lldb-dev wrote: > Hi, > > I've been working on a MacPorts port for lldb > There is already available framework with standalone build of LLDB for Darwin -- pkgsrc. So far it ships with local patches, but they are being eliminated. http://pkgsrc.se/devel/

Re: [lldb-dev] [llvm-dev] [Attn: Bot Owners!] Raising CMake minimum version to 3.4.3

NetBSD is ready (cmake-3.5.2). It now runs 7.0 kernel, 7.99.29 userland and newer GNU toolchain (GCC 5.3, LD 2.26). http://lab.llvm.org:8011/buildslaves/lldb-amd64-ninja-netbsd7 On 26.05.2016 18:57, Zachary Turner via lldb-dev wrote: > Windows LLDB is done > > On Thu, May 26, 2016 at 2:39 AM Da

Re: [lldb-dev] netbsd7 buildbot broken

you see fit (feel free to make a copy of the current > scripts). > > cheers, > pl > > > > On 25 May 2016 at 05:58, Kamil Rytarowski via lldb-dev > wrote: >> There is a change in build scripts from buildbot farm: >> >> + cmake -GNinja -DCMAKE_BUILD_

Re: [lldb-dev] netbsd7 buildbot broken

/../llvm -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++ -DLLDB_DISABLE_CURSES:BOOL=FALSE On 25.05.2016 02:22, Zachary Turner wrote: > There's no CMake change in any of these patches. It looks like > something is wrong with your bot. > > On Tue, May 24, 2016 at 5:14 PM Kamil Rytaro

[lldb-dev] netbsd7 buildbot broken

http://lab.llvm.org:8011/builders/lldb-amd64-ninja-netbsd7/builds/4296 It looks like after this build, scripts for bots were altered to require clang + clang++? I'm using the GNU toolchain. Could we please revert this enforcement? ___ lldb-dev mailing li

Re: [lldb-dev] [Attn: Bot Owners!] Raising CMake minimum version to 3.4.3

On 24.05.2016 22:54, Chris Bieneman via lldb-dev wrote: > Meant to send this yesterday, but I want to remind everyone that we’re going > to be raising the CMake minimum version to 3.4.3 next week. > > If you maintain bots please ensure that your bots are updated by end of day > 5/29 so that we c

Re: [lldb-dev] How to link lldb on i386

I had similar problems on NetBSD/amd64 - using standalone builds helped me. I'm building and installing LLVM, Clang and LLDB separately. It may help on i386. Also there might be a problem with using too many jobs. Try to build with -j1. On 24.05.2016 20:01, Siva Chandra via lldb-dev wrote: > We h

Re: [lldb-dev] Standalone build broken after r269332

In further changes please add me to review, I will test the standalone build. Yes, I'm running an installed version of llvm-config and I don't have sources neither build files. On 17.05.2016 10:05, Pavel Labath via lldb-dev wrote: > Ok, I see what the problem is now. If you run llvm-config from t

[lldb-dev] LLDB targeting NetBSD-8.0

I'm moving my efforts of porting LLDB from NetBSD-7.0 to NetBSD-8.0. I decided that 7.0 isn't worth more effort since libstdc++ is already too old (no ) and it misses support for debug registers and useful ptrace(2) interfaces for a full-process instrumentation. I'm going to upgrade the LLVM+Clan

Re: [lldb-dev] Standalone build broken after r269332

On 14.05.2016 02:46, Eugene Zelenko via lldb-dev wrote: > But biggest problem remains is how to specify Clang source and build > directories, since llvm-config doesn't tells about them. The requirement of source-code of Clang+LLVM and build dirs of Clang and LLVM is no-go in a package-manager use-

[lldb-dev] Push work-in-progress plugin for Process NetBSD?

I keep locally almost 5k lines of code of the process plugin for NetBSD. It's still not functional (there are bugs), but it has all or mostly all of the code needed for amd64. Is it fine to push it upstream and continue development against the version in-tree? My code is based on FreeBSD with rem

Re: [lldb-dev] Redundant six.py copy

gt; -- >> Qualcomm Innovation Center, Inc. >> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a >> Linux Foundation Collaborative Project >> >>> -----Original Message- >>> From: lldb-dev [mailto:lldb-dev-boun...@lists.ll

Re: [lldb-dev] Redundant six.py copy

On 02.05.2016 18:40, Reid Kleckner wrote: > On Sun, May 1, 2016 at 2:21 PM, Kamil Rytarowski via lldb-dev > mailto:lldb-dev@lists.llvm.org>> wrote: > > It has been noted that LLDB installs its own copy of six.py > (third_party/Python/module/six/six.py) that confli

Re: [lldb-dev] Redundant six.py copy

you need to install six before you can use > lldb", but given the number of different ways in which people use it and > the different needs, this isn't ideal. > > There are no plans to drop support for 2.7, so it will continue to be > needed. Do you actually get an error

[lldb-dev] Redundant six.py copy

It has been noted that LLDB installs its own copy of six.py (third_party/Python/module/six/six.py) that conflicts with a standalone one lang/py-six (path in pkgsrc). Could we reuse an external version shipped with a system? Alternatively are there plans to migrate to Python 3 and remove need for i

Re: [lldb-dev] Interest in enabling -Werror by default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 NetBSD builds with GCC 4.8.2 and it emits few warnings for LLDB. Before enabling -Werror please first iterate over build logs and help to squash them. For example it detects undefined behavior IIRC for a Darwin code part. On 16.02.2016 20:01, Zacha

Re: [lldb-dev] LLDB/NetBSD test suite results as of 8 Dec 2015

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08.12.2015 17:21, Ed Maste wrote: > On 7 December 2015 at 19:28, Kamil Rytarowski via lldb-dev > wrote: >> >> I ran the LLDB test suite of the LLDB-current version on >> NetBSD/amd64 (v. 7.99.21). >> >> Th

[lldb-dev] LLDB/NetBSD test suite results as of 8 Dec 2015

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I ran the LLDB test suite of the LLDB-current version on NetBSD/amd64 (v. 7.99.21). The results are as follows: 415 out of 415 test suites processed - TestRecursiveTypes.py Ran 415 test suites (266 failed) (64.096386%) Ran 222 test cases (145 fail

Re: [lldb-dev] LLDB and Swift

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Very nice. Congrats on your release! On 04.12.2015 00:03, Todd Fiala via lldb-dev wrote: > Hi all, > > Earlier today, you may have heard that Swift went open source over > at swift.org . I just wanted to take a moment > to ment

Re: [lldb-dev] Exclusively build and install LLDB?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Compatibility with wide range of LLVM or Clang releases is out of scope. On 02.12.2015 17:38, Todd Fiala wrote: > Yes, that concept came out in the thread. I just wanted to make > sure there wasn't also a desire to park on a version of llvm/clang,

Re: [lldb-dev] Exclusively build and install LLDB?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02.12.2015 19:36, Jim Ingham wrote: > Todd is right, at runtime lldb does need to find some of the clang > include files in order to build modules for its own purposes. On > an OS X install, these headers are put in: > > LLDB.framework/Resources

Re: [lldb-dev] Exclusively build and install LLDB?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 27.11.2015 00:57, Kamil Rytarowski via lldb-dev wrote: > On 11/23/15 10:28, Pavel Labath wrote: >> I believe that for purposes of building distribution packages you >> should use the out-of-tree mode of building lldb. This mean

Re: [lldb-dev] Exclusively build and install LLDB?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/23/15 10:28, Pavel Labath wrote: > I believe that for purposes of building distribution packages you > should use the out-of-tree mode of building lldb. This means, you > build llvm and clang separately, and then point your LLDB build to > t

Re: [lldb-dev] Exclusively build and install LLDB?

here: http://wip.pkgsrc.org/cgi-bin/gitweb.cgi?p=pkgsrc-wip.git;a=blob_plain;f =lldb-git/Makefile GH mirror: https://github.com/NetBSD/pkgsrc-wip/blob/master/lldb-git/Makefile Thanks! > On Sun, Nov 22, 2015 at 5:44 PM Kamil Rytarowski via lldb-dev > mailto:lldb-dev@lists.llvm.org>> w

[lldb-dev] Exclusively build and install LLDB?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Are there plans to add new target: lldb-only and lldb-install? There are already similar targets for Clang. I'm debugging LLDB on NetBSD and I'm having very bad time building everything with debug symbols. There is also popular request from NetBSD u

Re: [lldb-dev] Preliminary support for NetBSD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 21.10.2015 12:47, Kamil Rytarowski via lldb-dev wrote: > On 08.10.2015 12:21, Kamil Rytarowski via lldb-dev wrote: >> On 05.10.2015 21:46, Todd Fiala wrote: >>> Seems like a great idea. (Ed, is that something you might be

Re: [lldb-dev] Preliminary support for NetBSD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08.10.2015 12:21, Kamil Rytarowski via lldb-dev wrote: > On 05.10.2015 21:46, Todd Fiala wrote: >> Seems like a great idea. (Ed, is that something you might be >> able to review?) > > > The first patch is a

Re: [lldb-dev] Does anyone depend on using LLDB with Python 2.6?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 (NetBSD) Python 2.6 was retired with pkgsrc-2015Q2 http://mail-index.netbsd.org/pkgsrc-users/2015/07/06/msg021778.html On 19.10.2015 21:43, Zachary Turner via lldb-dev wrote: > AKA: Is Python 2.6 a supported configuration? I found this > `argpars

Re: [lldb-dev] Preliminary support for NetBSD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05.10.2015 21:46, Todd Fiala wrote: > Seems like a great idea. (Ed, is that something you might be able > to review?) > The first patch is already proposed: http://reviews.llvm.org/D13334 > Hopefully you have access to other platforms to test

[lldb-dev] Preliminary support for NetBSD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I'm working on the NetBSD support for LLDB/LLVM. My current status is that it already builds and runs with my local patches. Unfortunatelly it still doesn't work due to (at least) ptrace(2) differences with the FreeBSD code. I would like to