Re: [lldb-dev] [3.8 Release] RC1 has been tagged

ARM and AArch64 seem both good. Uploaded. On 19 January 2016 at 23:47, Hans Wennborg wrote: > Dear testers, > > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at > r258223. (It took a little longer than I'd planned, sorry about that.) > > There are still a bunch of open merge r

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

On 20 January 2016 at 09:31, Sylvestre Ledru wrote: > What about creating a release management mailing list ? > The testers are usually the same (hello folks!) :) I second that! It'd also be much easier on mail filters... :) --renato ___ lldb-dev maili

Re: [lldb-dev] Inquiry for performance monitors

n, add options and arguments as needed > to this command). The python code could bridge to C and use the intel > libraries that know how to process the data. > > > > If this all goes well we can think about building it into LLDB as a > built in command. > > > >

Re: [lldb-dev] marking new summary output for expected timeouts

Great. Actually there is a latent bug in there we hit yesterday, when there is a platform set but it doesn't start with "remote-" (we assume the match result has a first matched group and blow up). I'll submit a patch that both fixes that up and strips out the darwin ones. I think the rerun logi

Re: [lldb-dev] clang-format now supports return type on separate line

Glad to see clang-format getting some improvements. On Thu, Jan 7, 2016 at 10:30 AM, Zachary Turner wrote: > As far as I'm aware, this is the last major incompatibility between LLDB's > style and clang-format's feature set. > > I would appreciate it if more people could try it out with a few o

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

On Wed, Jan 20, 2016 at 5:02 PM, Ben Pope via cfe-dev wrote: > On Thursday, January 21, 2016 01:28 AM, Hans Wennborg via cfe-dev wrote: >> >> On Wed, Jan 20, 2016 at 7:54 AM, Ben Pope wrote: >>> >>> On Wednesday, January 20, 2016 07:47 AM, Hans Wennborg wrote: Dear testers, >>

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

On Thu, Jan 21, 2016 at 5:18 AM, Renato Golin wrote: > On 20 January 2016 at 09:31, Sylvestre Ledru wrote: >> What about creating a release management mailing list ? >> The testers are usually the same (hello folks!) :) > > I second that! It'd also be much easier on mail filters... :) Tanya, can

Re: [lldb-dev] clang-format now supports return type on separate line

I'm not sure I agree. I don't think anything will be awkwardly formatted with regards to the rest of the file. The biggest thing this is going to fix are whitespace at the end of lines, line breakign conventions, and space between function name and parentheses. If we're not going to enforce a co

[lldb-dev] Problems with core load on Linux and proposed solution

Hi, LLDB 3.8 has much better support for core load on Linux than 3.7 - thanks a lot! But there are still two problems. 1. The thread ID are lost and there is FIXME in the code2. If core dump is obtained from live process (i.e. gdb attach, gcore, detach) then there is no thread that has any reaso

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

On 20 Jan 2016, at 22:26, Hans Wennborg wrote: > > On Wed, Jan 20, 2016 at 12:18 PM, Dimitry Andric wrote: ... >> The way I fixed this during the 3.7 test phase, is by changing >> test-release.sh so it exports directly into these locations: >> >> # Exporting llvm 3.7.0-rc3 sources to llvm.src

Re: [lldb-dev] clang-format now supports return type on separate line

Also this is the same standard that applies to the rest of LLVM. clang-format your patches. Just because we haven't been consistently following the rules until now doesn't mean we should continue to not follow the rules going forward. This way eventually the codebase slowly converges towards a p

Re: [lldb-dev] [llvm-dev] [3.8 Release] RC1 has been tagged

On 20 Jan 2016, at 21:18, Dimitry Andric via llvm-dev wrote: ... >>> * Last but not least: the host compiler on FreeBSD 10.x is clang 3.4.1 (the >>> last version that can build without C++11 support), and it crashes with a >>> segfault during building of CGBlocks.cpp. I'll need to find some wa

Re: [lldb-dev] clang-format now supports return type on separate line

ormat”? That could be also interpreted as a “// TODO add comments so what this does is more understandable” Sean > On Jan 21, 2016, at 10:59 AM, Zachary Turner via lldb-dev > wrote: > > Also this is the same standard that applies to the rest of LLVM. > clang-format your patch

Re: [lldb-dev] clang-format now supports return type on separate line

e understandable” > > Sean > > On Jan 21, 2016, at 10:59 AM, Zachary Turner via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > Also this is the same standard that applies to the rest of LLVM. > clang-format your patches. Just because we haven't been consistentl

Re: [lldb-dev] clang-format now supports return type on separate line

On Thu, Jan 21, 2016 at 11:18 AM Sean Callanan wrote: > I tend to agree with Zachary on the overall principle – and I would be > willing to clang-format functions when I modify them. I’m concerned about > a specific class of functions, though. Let’s say I have a function that > has had lots of

Re: [lldb-dev] Inquiry for performance monitors

emory and hand it to > > the Intel PT stuff. The "intel-pt-dump" could just give a raw dump all of > > history for one or more threads (again, add options and arguments as needed > > to this command). The python code could bridge to C and use the intel > > l

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg wrote: > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at > r258223. (It took a little longer than I'd planned, sorry about that.) > > There are still a bunch of open merge requests and bug reports, but I > wanted to get the tag in

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

SuSE Linux Enterprise Server 11SP3 x86_64 Looks like I see several failures that weren't in 3.7.1. Is there any way to tell whether these are regressions vs new-to-3.8.0-but-failing? The MSan ones were in 3.7.1 but the ThreadPoolTest and the libc++ errors were not in 3.7.1. Fai

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev < cfe-...@lists.llvm.org> wrote: > SuSE Linux Enterprise Server 11SP3 x86_64 > > Looks like I see several failures that weren't in 3.7.1. Is there any way > to tell whether these are regressions vs new-to-3.8.0-but-failing? The > MSan ones

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

On Wed, Jan 20, 2016 at 1:18 PM, Dimitry Andric via cfe-dev < cfe-...@lists.llvm.org> wrote: > On 20 Jan 2016, at 18:23, Hans Wennborg wrote: > > > > On Wed, Jan 20, 2016 at 5:25 AM, Dimitry Andric > wrote: > >> Unfortunately I'm having lots of trouble with rc1 at this point: > >> * libcxxabi ca

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

On Thu, Jan 21, 2016 at 8:31 PM, Eric Fiselier wrote: > > On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev < > cfe-...@lists.llvm.org> wrote: > >> SuSE Linux Enterprise Server 11SP3 x86_64 >> >> Looks like I see several failures that weren't in 3.7.1. Is there any >> way to tell whether t

Re: [lldb-dev] clang-format now supports return type on separate line

Okay, sounds like a reasonable thing to try. We can always review it if it causes any real issues. On Thu, Jan 21, 2016 at 11:34 AM, Zachary Turner wrote: > > > On Thu, Jan 21, 2016 at 11:18 AM Sean Callanan > wrote: > >> I tend to agree with Zachary on the overall principle – and I would be >

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

Something is failing on 32bit Fedora 23 (compiler-rt?), test suite looks good. On Fri, Jan 22, 2016 at 2:52 PM, Brian Cain via cfe-dev < cfe-...@lists.llvm.org> wrote: > On Thu, Jan 21, 2016 at 8:31 PM, Eric Fiselier wrote: > >> >> On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev < >> cfe

Re: [lldb-dev] clang-format now supports return type on separate line

examples where the automated approach is imperfect. Kate Stone k8st...@apple.com  Xcode Runtime Analysis Tools > On Jan 21, 2016, at 9:46 PM, Todd Fiala via lldb-dev > wrote: > > Okay, sounds like a reasonable thing to try. We can always review it if it > causes any real issue

Re: [lldb-dev] clang-format now supports return type on separate line

d lead to discussions about concrete > examples where the automated approach is imperfect. > > Kate Stone k8st...@apple.com >  Xcode Runtime Analysis Tools > > On Jan 21, 2016, at 9:46 PM, Todd Fiala via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > Okay, sounds like

Re: [lldb-dev] clang-format now supports return type on separate line

edge that there may be cases >> where this produces undesirable results. Manual formatting to correct >> these issues is acceptable and should lead to discussions about concrete >> examples where the automated approach is imperfect. >> >> Kate Stone k8st...@apple.com

Re: [lldb-dev] LLDB test questions

Hi Ted! I hope you don't mind - I'm going to CC lldb-dev since there is some useful general info in here for others who are getting started with the test system. (And others can fact-check anything I may gloss over here). On Thu, Jan 21, 2016 at 2:00 PM, Ted Woodward wrote: > Hi Todd, > > > >

[lldb-dev] Ubuntu version-based fail/skip

Hey all, What do you think about having some kind of way of marking the (in this case, specifically) Ubuntu distribution for fail/skip test decorators? I've had a few cases where I've needed to mark tests failing on for Ubuntu where it really was only a particular release of an Ubuntu distribution

Re: [lldb-dev] [3.8 Release] Schedule and call for testers

On Fri, Dec 11, 2015 at 3:14 PM, Hans Wennborg wrote: > It's not quite time to start the 3.8 release process, but it's time to > start planning. > > Please let me know if you want to help with testing and building > release binaries for your favourite platform. (If you were a tester on > the previ

Re: [lldb-dev] lldb status at windows

le in certain scenarios >>> * Conditional breakpoints don't work >>> * Hardware watchpoints don't work >>> * Expression evaluation might not work in some advanced cases. >>> >>> The main big feature that has been added since the original blog post

Re: [lldb-dev] lldb status at windows

gt;>>> * Expression evaluation might not work in some advanced cases. >>>> >>>> The main big feature that has been added since the original blog post >>>> is support for windows minidump files. So you can create a minidump of a >>>> stopped

Re: [lldb-dev] lldb status at windows

atus on the website. Here's my best estimate at what you can expect. >>>>> >>>>> * Most common debugging scenarios should work. Run under debugger, >>>>> attach to process, interrupt, continue, print variable values, evaluate >>>>> e

Re: [lldb-dev] clang-format now supports return type on separate line

-format off */ up to a comment // clang-format on or /* clang-format on */ will not be formatted. The comments themselves will be formatted (aligned) normally. - On 22 January 2016 at 17:09, Todd Fiala via lldb-dev wrote: > Okay, thanks for the tip! > > On Fri, Jan 22, 2016 a

Re: [lldb-dev] lldb status at windows

x27;t >>>>> work is a bug that I would like to fix. >>>>> >>>>> On Thu, Jan 7, 2016 at 10:02 AM Zachary Turner >>>>> wrote: >>>>> >>>>>> Hi, I guess I should make a

Re: [lldb-dev] clang-format now supports return type on separate line

g-format off */ up to a comment // clang-format on or /* > clang-format on */ will not be formatted. The comments themselves will > be formatted (aligned) normally. > - > > > On 22 January 2016 at 17:09, Todd Fiala via lldb-dev > wrote: > > Okay, thanks for the tip! > &

Re: [lldb-dev] lldb status at windows

On Fri, Jan 22, 2016 at 3:30 PM, Zachary Turner via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Under llvm/tools also checkout lld. So your directories should look like > this: > > llvm > \-- tools > \-- clang > \-- lldb > \-- lld > > Then re-run

Re: [lldb-dev] clang-format now supports return type on separate line

PM, Pavel Labath via lldb-dev > wrote: > > Apparently, you can also disable the formatting of a piece of code by > a magic comment. Could be quite useful for those tables. From the > docs: > - > Clang-format understands also special comments that switch formatting > in

Re: [lldb-dev] clang-format now supports return type on separate line

rns about tables. > I have to say, I always feel good vibes about a source base when they have > lint directives in comments. Shows they run lint as a matter of course. > > Sean > > > On Jan 22, 2016, at 12:29 PM, Pavel Labath via lldb-dev < > lldb-dev@lists.llvm.org>

[lldb-dev] [3.8 Release] Release Candidate 1 source and binaries available

Hello everyone, Source and binaries for LLVM-3.8.0-rc1 are now available at http://llvm.org/pre-releases/3.8.0/ (Binaries for some platforms are still missing, but I figured it was time to get this out there.) Please try it, run tests, build your favourite projects, and *file bugs* about anythin

[lldb-dev] LLDB OS X buildbot/testbot details

Hi all, The llvm.org Green Dragon (i.e. Jenkins-based) LLDB OS X buildbot/testbot has received some improvements today. The Jenkins build now uses the xUnit plugin to process xUnit-based test suite results, which are displayed more usefully on the "build and test" page here

Re: [lldb-dev] lldb status at windows

ina : >>>> >>>>> Nice to hear. I should answer after some time of using >>>>> >>>>> 2016-01-07 21:04 GMT+03:00 Zachary Turner : >>>>> >>>>>> Feel free to file bugs or post your feedback here after you use ab

Re: [lldb-dev] lldb status at windows

> >>>>> ----------- >>>>> a.exe and lldb hangs >>>>> >>>>> What i doing wrong ? >>>>> >>>>> >>>>> 2016-01-08 0:42 GMT+03:00 Red Skotina : >>>>> >>>

Re: [lldb-dev] lldb status at windows

argv) >>>>>> { >>>>>> printf("hello1\n"); >>>>>> printf("hello2\n"); >>>>>> return 0; >>>>>> } >>>>>> >>>>>> d:\code\test

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

Two libc++ tests fail on 64bit Fedora 23, get_monthname and get_monthname_wide. Test suite looks good. On Fri, Jan 22, 2016 at 10:09 PM, Nikola Smiljanic wrote: > Something is failing on 32bit Fedora 23 (compiler-rt?), test suite looks > good. > > On Fri, Jan 22, 2016 at 2:52 PM, Brian Cain via

Re: [lldb-dev] lldb status at windows

tdlib, from vs2015 >>>>>>> x86 >>>>>>> developer console . >>>>>>> i use lldb from trunk >>>>>>> #include "stdio.h" >>>>>>> >>>>>>> int main(int arg

Re: [lldb-dev] lldb status at windows

>> >>>>>>> On Fri, Jan 22, 2016 at 11:08 AM Red Skotina >>>>>>> wrote: >>>>>>> >>>>>>>> Look like I miss something , but i cant debug simple program >>>>>>>> pr

Re: [lldb-dev] lldb status at windows

gt;>>>> What's the command line you used with clang? >>>>>>> >>>>>>> On Fri, Jan 22, 2016 at 11:08 AM Red Skotina >>>>>>> wrote: >>>>>>> >>>>>>>> Look like I m

[lldb-dev] On Debian [was: Re: [3.8 Release] RC1 has been tagged]

Le 20/01/2016 00:47, Hans Wennborg a écrit : > Dear testers, > > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at > r258223. (It took a little longer than I'd planned, sorry about that.) > > There are still a bunch of open merge requests and bug reports, but I > wanted to get th

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

On Thu, Jan 21, 2016 at 9:52 PM, Brian Cain wrote: > On Thu, Jan 21, 2016 at 8:31 PM, Eric Fiselier wrote: > >> >> On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev < >> cfe-...@lists.llvm.org> wrote: >> >>> SuSE Linux Enterprise Server 11SP3 x86_64 >>> >>> Looks like I see several failure

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

I built rc1 on Ubuntu 15.04 armhf. Many tests fail (560, nearly all are libc++ and libc++abi). There's also a handful of unexpected passing tests (12). e29ac68df06f7fad8c773b7da9778469d84f3f32 rc1/clang+llvm-3.8.0-rc1-linux-armhf-vivid.tar.xz On Tue, Jan 19, 2016 at 5:47 PM, Hans Wennborg wr

[lldb-dev] Selectively disabling value formatter

Hi, If I have an SBValue for an object whose type has a formatter enabled for it, is there a way to detect this via the Python API, and if so, request an "unmodified" view of the object? I've experimented with value.IsSynthetic() and value.GetNonSyntheticValue(), but the former seems to always retu

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

I have some proper rc1 results now. clang+llvm-3.8.0-rc1-mips-linux-gnu.tar.xz test-release.sh refused to run 'make check-all' because libcxx_tsan failed to configure. This is because the thread sanitizer is not supported on MIPS32. After working around this (patch will follow sh

Re: [lldb-dev] Ubuntu version-based fail/skip

I think recently we are trying to reduce the number of decorators we are having so adding a few new Ubuntu specific decorators might not be a good idea. My suggestion would be to move on a little bit to the functional programming style with adding a new option to @expetedFailureAll where we can spe

Re: [lldb-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

On Sun, Jan 24, 2016 at 2:48 PM, Brian Cain wrote: > > On Thu, Jan 21, 2016 at 9:52 PM, Brian Cain wrote: >> >> On Thu, Jan 21, 2016 at 8:31 PM, Eric Fiselier wrote: >>> >>> >>> On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev >>> wrote: SuSE Linux Enterprise Server 11SP3 x86_6

Re: [lldb-dev] Patch to fix REPL for ARMv7 & ARMv6 on linux

This patch looks reasonable to me, but I don't know enough about LLDB to actually review it. +Renato or Pavel maybe? On Thu, Jan 14, 2016 at 11:32 AM, William Dillon via lldb-dev wrote: > Hi again, everyone > > I’d like to ping on this patch now that the 3.8 branch is fairly new,

Re: [lldb-dev] Selectively disabling value formatter

> On Jan 25, 2016, at 12:23 AM, Vadim Chugunov via lldb-dev > wrote: > > Hi, > If I have an SBValue for an object whose type has a formatter enabled for it, > is there a way to detect this via the Python API, and if so, request an > "unmodified" view of the obj

[lldb-dev] Bad state of release 3.7.1?

Hi, My colleague downloaded and built 3.7.1 version of lldb on Linux. When we used it to attach to a normal process(like sleep), it just hangs forever: bin/lldb -n sleep (lldb) process attach --name "sleep" And my private built 3.8.0 version works fine. Just to confirm, is 3.7.1 a bad version?

Re: [lldb-dev] Selectively disabling value formatter

On Mon, Jan 25, 2016 at 11:04 AM, Enrico Granata wrote: > > On Jan 25, 2016, at 12:23 AM, Vadim Chugunov via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > Hi, > If I have an SBValue for an object whose type has a formatter enabled for > it, is there a way to det

Re: [lldb-dev] Selectively disabling value formatter

> On Jan 25, 2016, at 3:20 PM, Vadim Chugunov wrote: > > On Mon, Jan 25, 2016 at 11:04 AM, Enrico Granata <mailto:egran...@apple.com>> wrote: > >> On Jan 25, 2016, at 12:23 AM, Vadim Chugunov via lldb-dev >> mailto:lldb-dev@lists.llvm.org>> wrote: &g

Re: [lldb-dev] Bad state of release 3.7.1?

Btw: here is the source that we built lldb from: http://llvm.org/releases/download.html#3.7.1 direct link http://llvm.org/releases/3.7.1/lldb-3.7.1.src.tar.xz On Mon, Jan 25, 2016 at 2:37 PM, Jeffrey Tan wrote: > Hi, > > My colleague downloaded and built 3.7.1 version of lldb on Linux. When we

Re: [lldb-dev] Selectively disabling value formatter

On Mon, Jan 25, 2016 at 12:23 AM, Vadim Chugunov via lldb-dev wrote: > Hi, > If I have an SBValue for an object whose type has a formatter enabled for > it, is there a way to detect this via the Python API, and if so, request an > "unmodified" view of the object? &g

Re: [lldb-dev] Selectively disabling value formatter

lldb-340.4.119 (OSX 10.11.3) On Mon, Jan 25, 2016 at 3:42 PM, Siva Chandra wrote: > On Mon, Jan 25, 2016 at 12:23 AM, Vadim Chugunov via lldb-dev > wrote: > > Hi, > > If I have an SBValue for an object whose type has a formatter enabled for > > it, is there a way to de

Re: [lldb-dev] Selectively disabling value formatter

16 at 12:23 AM, Vadim Chugunov via lldb-dev >> wrote: >> > Hi, >> > If I have an SBValue for an object whose type has a formatter enabled >> > for >> > it, is there a way to detect this via the Python API, and if so, request >> > an >> > &qu

Re: [lldb-dev] Selectively disabling value formatter

> On Jan 25, 2016, at 4:04 PM, Vadim Chugunov wrote: > > > > On Mon, Jan 25, 2016 at 3:31 PM, Enrico Granata > wrote: > >> >> Whose IsSynthetic() is supposed to return True,- the parent's or the >> child's? > > What do you mean with this? > The model is that y

Re: [lldb-dev] Selectively disabling value formatter

> On Jan 25, 2016, at 4:09 PM, Vadim Chugunov via lldb-dev > wrote: > > lldb-340.4.119 (OSX 10.11.3) > > On Mon, Jan 25, 2016 at 3:42 PM, Siva Chandra <mailto:sivachan...@google.com>> wrote: > On Mon, Jan 25, 2016 at 12:23 AM, Vadim Chugunov via lldb-dev &g

Re: [lldb-dev] Bad state of release 3.7.1?

Jan 25, 2016 at 4:12 PM, David Jones wrote: > This is a known problem with 3.7.1. > > It should be fixed for 3.8. You should be able to try out 3.8rc1 right now. > > > > On Mon, Jan 25, 2016 at 5:37 PM, Jeffrey Tan via lldb-dev < > lldb-dev@lists.llvm.org> wrote: >

Re: [lldb-dev] Bad state of release 3.7.1?

. >> >> It should be fixed for 3.8. You should be able to try out 3.8rc1 right >> now. >> >> >> >> On Mon, Jan 25, 2016 at 5:37 PM, Jeffrey Tan via lldb-dev < >> lldb-dev@lists.llvm.org> wrote: >> >>> Hi, >>> >>> M

Re: [lldb-dev] Selectively disabling value formatter

I think this one: http://llvm.org/viewvc/llvm-project?view=revision&revision=240578 On Mon, Jan 25, 2016 at 4:34 PM, Enrico Granata wrote: > > On Jan 25, 2016, at 4:09 PM, Vadim Chugunov via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > lldb-340.4.119 (OSX 10.11.3)

Re: [lldb-dev] Selectively disabling value formatter

Granata <mailto:egran...@apple.com>> wrote: > >> On Jan 25, 2016, at 4:09 PM, Vadim Chugunov via lldb-dev >> mailto:lldb-dev@lists.llvm.org>> wrote: >> >> lldb-340.4.119 (OSX 10.11.3) >> >> On Mon, Jan 25, 2016 at 3:42 PM, Siva Chandra >

Re: [lldb-dev] Bad state of release 3.7.1?

> >> On Mon, Jan 25, 2016 at 4:12 PM, David Jones >> wrote: >> >>> This is a known problem with 3.7.1. >>> >>> It should be fixed for 3.8. You should be able to try out 3.8rc1 right >>> now. >>> >>> >>> >>>

[lldb-dev] something just toasted the test suite on OS X

Not sure exactly what it is, but all the tests are failing due to some bad assumptions of unicode vs. str on Python 2 vs. 3 if I had to guess. I am not going to be able to look at details on that, but here's a link to the log on the OS X builder: http://lab.llvm.org:8080/green/job/lldb_build_test

Re: [lldb-dev] something just toasted the test suite on OS X

> On Jan 25, 2016, at 6:48 PM, Todd Fiala via lldb-dev > wrote: > > Not sure exactly what it is, but all the tests are failing due to some bad > assumptions of unicode vs. str on Python 2 vs. 3 if I had to guess. > Author: zturner Date: Mon Jan 25 18:59:42 2016 New Rev

Re: [lldb-dev] something just toasted the test suite on OS X

Well our whole test suite just stopped running, so yes. On Mon, Jan 25, 2016 at 6:58 PM, Enrico Granata wrote: > > On Jan 25, 2016, at 6:48 PM, Todd Fiala via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > Not sure exactly what it is, but all the tests are fa

Re: [lldb-dev] something just toasted the test suite on OS X

, Jan 25, 2016 at 8:25 PM, Todd Fiala wrote: > Well our whole test suite just stopped running, so yes. > > On Mon, Jan 25, 2016 at 6:58 PM, Enrico Granata > wrote: > >> >> On Jan 25, 2016, at 6:48 PM, Todd Fiala via lldb-dev < >> lldb-dev@lists.llvm.org>

Re: [lldb-dev] something just toasted the test suite on OS X

sorry, yea I stuck around for a while after that patch waiting for emails, but nothing came through. Please revert in the meantime, I'll work on a fix tomorrow. On Mon, Jan 25, 2016 at 8:52 PM Todd Fiala via lldb-dev < lldb-dev@lists.llvm.org> wrote: > I think I see what happene

Re: [lldb-dev] something just toasted the test suite on OS X

est output, I switched email over to the builder step, which >> doesn't know anything about who made which changes. So it didn't know who >> to put on the blame list for the broken build. Drats, I'll have to figure >> that out. >> >> I'd rea

Re: [lldb-dev] something just toasted the test suite on OS X

w. > >> On Mon, Jan 25, 2016 at 8:52 PM Todd Fiala via lldb-dev >> wrote: >> I think I see what happened w/r/t why no emails when out when the build went >> heavy red. (Well they went out internally, but not externally). When I >> made the change on Fri

Re: [lldb-dev] something just toasted the test suite on OS X

I'll work on a > fix tomorrow. > > On Mon, Jan 25, 2016 at 8:52 PM Todd Fiala via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > >> I think I see what happened w/r/t why no emails when out when the build >> went heavy red. (Well they went out internally, but n

Re: [lldb-dev] something just toasted the test suite on OS X

emails, > but nothing came through. Please revert in the meantime, I'll work on a > fix tomorrow. > > On Mon, Jan 25, 2016 at 8:52 PM Todd Fiala via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > >> I think I see what happened w/r/t why no emails when out when th

Re: [lldb-dev] something just toasted the test suite on OS X

a while after that patch waiting for >> emails, but nothing came through. Please revert in the meantime, I'll work >> on a fix tomorrow. >> >> On Mon, Jan 25, 2016 at 8:52 PM Todd Fiala via lldb-dev < >> lldb-dev@lists.llvm.org> wrote: >> >>> I t

Re: [lldb-dev] something just toasted the test suite on OS X

ll to print. >> >> On Mon, Jan 25, 2016 at 8:54 PM Zachary Turner >> wrote: >> >>> sorry, yea I stuck around for a while after that patch waiting for >>> emails, but nothing came through. Please revert in the meantime, I'll work >>> on a fix tom

Re: [lldb-dev] something just toasted the test suite on OS X

o the file. >>> >>> What's the pattern you're referring to? You can't convert a string to a >>> unicode without specifying an encoding, and it seems annoying to have to do >>> that on every single call to print. >>> >>> On Mon, Jan 2

Re: [lldb-dev] Bad state of release 3.7.1?

hain, if you need it. The only requirement is that you build lldb with the matching version of llvm. regards, pl On 26 January 2016 at 01:36, David Jones via lldb-dev wrote: > r246756 has a fix, if you are comfortable applying it. It's a large patch. > In theory it should back-port b

Re: [lldb-dev] Patch to fix REPL for ARMv7 & ARMv6 on linux

gh about LLDB > to actually review it. > > +Renato or Pavel maybe? > > On Thu, Jan 14, 2016 at 11:32 AM, William Dillon via lldb-dev > wrote: >> Hi again, everyone >> >> I’d like to ping on this patch now that the 3.8 branch is fairly new, and >> merging it o

Re: [lldb-dev] [cfe-dev] [llvm-dev] [3.8 Release] RC1 has been tagged

The test-suite shouldn't be being build with CMake for the release - the CMake system is not yet ready. Have you accidentally checked out the test-suite into /projects? if it's there it will auto-configure. James On Tue, 26 Jan 2016 at 16:01 Ismail Donmez via cfe-dev < cfe-...@lists.llvm.org> wro

Re: [lldb-dev] [cfe-dev] [llvm-dev] [3.8 Release] RC1 has been tagged

If the test-suite setup with CMake is broken, why not replace the CMake auto-detection of the test-suite with an error? Something like: diff --git a/CMakeLists.txt b/CMakeLists.txt index d96afc465177..918da6f6c945 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -693,11 +693,7 @@ endif() if

Re: [lldb-dev] something just toasted the test suite on OS X

and return the number of characters written. >>>> So clearly it does have to be a unicode object, and saying >>>> print(self.getvalue(), file=self.session) is clearly NOT printing a unicode >>>> string to the file. >>>> >>>> What's

Re: [lldb-dev] something just toasted the test suite on OS X

tml#unicode> string *s* to >>>>> the stream and return the number of characters written. >>>>> So clearly it does have to be a unicode object, and saying >>>>> print(self.getvalue(), file=self.session) is clearly NOT printing a >>>>> unicode

Re: [lldb-dev] something just toasted the test suite on OS X

gt; >>>>>> Write the unicode >>>>>> <https://docs.python.org/2/library/functions.html#unicode> string *s* to >>>>>> the stream and return the number of characters written. >>>>>> So clearly it does have to be a unicode

Re: [lldb-dev] something just toasted the test suite on OS X

king at the >>>>>>> documentation for io.write object, i see this: >>>>>>> >>>>>>> write(*s*) >>>>>>> <https://docs.python.org/2/library/io.html#io.TextIOBase.write> >>>>>>> >>>>&

Re: [lldb-dev] something just toasted the test suite on OS X

type of the string/bytes you give >>>>>>> it, >>>>>>> and makes sure it becomes what you need. It's going to assume an >>>>>>> encoding >>>>>>> like utf-8. >>>>>>> >>>>>&

[lldb-dev] LLDB Windows MSVC buildbot out of memory errors

Hi all, Cross posting to all groups because I'm getting a lot of email about this recently. Changes that have gone into clang over the past few months have increased the strain on the linker, and it's to the point that MSVC cannot link libclang.dll without going over the memory limits of a a 32-b

Re: [lldb-dev] Patch to fix REPL for ARMv7 & ARMv6 on linux

't know enough about LLDB >> to actually review it. >> >> +Renato or Pavel maybe? >> >> On Thu, Jan 14, 2016 at 11:32 AM, William Dillon via lldb-dev >> wrote: >>> Hi again, everyone >>> >>> I’d like to ping on this patch no

Re: [lldb-dev] [llvm-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

> Have you accidentally checked out the test-suite into /projects? if it's > there it will auto-configure We fixed it for rc1 but test-release.sh used to put the test-suite there. From: llvm-dev [mailto:llvm-dev-boun...@lists.llvm.org] On Behalf Of James Molloy via llvm-dev Sent: 26 January 201

[lldb-dev] Fixing OS X Xcode build

Hi all, At the current moment the OS X Xcode build is broken. I'll be working on fixing it today. As has been discussed in the past, post llvm/clang-3.8 the configure/automake system was getting stripped out of LLVM and clang. The OS X Xcode build has a legacy step in it that still uses the conf

Re: [lldb-dev] something just toasted the test suite on OS X

icode or byte style strings, for both Python 2 and Python 3. >>>>>>>> Essentially you figure out what you want it to be in, and you write a >>>>>>>> couple helper routes to go in either the "to unicode" or the "to bytes" >>&

Re: [lldb-dev] Patch to fix REPL for ARMv7 & ARMv6 on linux

Hi Pavel, Will is trying to get this working downstream of here IIRC. Greg, can you have a look and see what you think of the patch? (Also see Pavel's comments). Thanks! -Todd On Wed, Jan 27, 2016 at 1:28 AM, Omair Javaid via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Hi Wi

Re: [lldb-dev] [llvm-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

It seems that test-release was fixed, thanks everyone. Builds are OK but I'd like to know where did test-suite go? All I see is the llvm.src directory, am I supposed to export test-suite myself? On Wed, Jan 27, 2016 at 9:47 PM, Daniel Sanders wrote: > > Have you accidentally checked out the test

Re: [lldb-dev] [llvm-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

I've been putting together a patch to bring that back and I've just posted it as http://reviews.llvm.org/D16679. From: Nikola Smiljanic [mailto:popiz...@gmail.com] Sent: 28 January 2016 02:00 To: Daniel Sanders Cc: James Molloy; Ismail Donmez; Ben Pope; cfe-dev; openmp-dev (openmp-...@lists.llvm

[lldb-dev] Module Cache improvements - RFC

Hello all, we are running into limitations of the current module download/caching system. A simple android application can link to about 46 megabytes worth of modules, and downloading that with our current transfer rates takes about 25 seconds. Much of the data we download this way is never actual

<    19   20   21   22   23   24   25   26   27   28   >